arch/arm/boot/dts/qcom/qcom-msm8926-samsung-matisselte.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/qcom/qcom-msm8926-samsung-matisselte.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/qcom/qcom-msm8926-samsung-matisselte.dts- Extension
.dts- Size
- 913 bytes
- Lines
- 43
- Domain
- Architecture Layer
- Bucket
- arch/arm
- Inferred role
- Architecture Layer: configuration, schema, or hardware description
- Status
- atlas-only
Why This File Exists
CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
- CPU and platform-specific kernel glue: boot entry, traps, syscall entry, interrupts, page tables, context switch, and low-level barriers.
Dependency Surface
msm8926.dtsiqcom-msm8226-samsung-matisse-common.dtsi
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: BSD-3-Clause
/*
* Copyright (c) 2022, Matti Lehtimäki <matti.lehtimaki@gmail.com>
* Copyright (c) 2023, Stefan Hansson <newbyte@postmarketos.org>
*/
/dts-v1/;
#include "msm8926.dtsi"
#include "qcom-msm8226-samsung-matisse-common.dtsi"
/ {
model = "Samsung Galaxy Tab 4 10.1 LTE";
compatible = "samsung,matisselte", "qcom,msm8926", "qcom,msm8226";
chassis-type = "tablet";
reg_tsp_3p3v: regulator-tsp-3p3v {
compatible = "regulator-fixed";
regulator-name = "tsp_3p3v";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
gpio = <&tlmm 32 GPIO_ACTIVE_HIGH>;
enable-active-high;
pinctrl-names = "default";
pinctrl-0 = <&tsp_en1_default_state>;
};
};
&modem {
mss-supply = <&pm8226_s5>;
};
&tlmm {
tsp_en1_default_state: tsp-en1-default-state {
pins = "gpio32";
function = "gpio";
drive-strength = <2>;
bias-disable;
};
};
Annotation
- Immediate include surface: `msm8926.dtsi`, `qcom-msm8226-samsung-matisse-common.dtsi`.
- Atlas domain: Architecture Layer / arch/arm.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.