arch/arm64/boot/dts/qcom/msm8916-samsung-j3ltetw.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/qcom/msm8916-samsung-j3ltetw.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/qcom/msm8916-samsung-j3ltetw.dts- Extension
.dts- Size
- 626 bytes
- Lines
- 32
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- 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
msm8916-samsung-j3-common.dtsi
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-only
/dts-v1/;
#include "msm8916-samsung-j3-common.dtsi"
/ {
model = "Samsung Galaxy J3 (2016) (SM-J320YZ)";
compatible = "samsung,j3ltetw", "qcom,msm8916";
chassis-type = "handset";
};
&i2c_muic {
sda-gpios = <&tlmm 0 (GPIO_ACTIVE_HIGH|GPIO_OPEN_DRAIN)>;
scl-gpios = <&tlmm 1 (GPIO_ACTIVE_HIGH|GPIO_OPEN_DRAIN)>;
};
&i2c_sensors {
/* I2C2 */
sda-gpios = <&tlmm 6 (GPIO_ACTIVE_HIGH|GPIO_OPEN_DRAIN)>;
scl-gpios = <&tlmm 7 (GPIO_ACTIVE_HIGH|GPIO_OPEN_DRAIN)>;
};
&muic_i2c_default {
pins = "gpio0", "gpio1";
};
&sensors_i2c_default {
/* I2C2 */
pins = "gpio6", "gpio7";
};
Annotation
- Immediate include surface: `msm8916-samsung-j3-common.dtsi`.
- Atlas domain: Architecture Layer / arch/arm64.
- 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.