arch/arm64/boot/dts/qcom/msm8916-samsung-grandprimelte.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/qcom/msm8916-samsung-grandprimelte.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/qcom/msm8916-samsung-grandprimelte.dts- Extension
.dts- Size
- 809 bytes
- Lines
- 49
- 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-fortuna-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-fortuna-common.dtsi"
/ {
model = "Samsung Galaxy Grand Prime (SM-G530FZ)";
compatible = "samsung,grandprimelte", "qcom,msm8916";
chassis-type = "handset";
};
&battery {
charge-term-current-microamp = <200000>;
constant-charge-current-max-microamp = <1000000>;
constant-charge-voltage-max-microvolt = <4350000>;
};
&bosch_accel {
status = "okay";
};
&bosch_magn {
status = "okay";
};
&charger {
richtek,usb-connector = <&usb_con_sm5502>;
status = "okay";
};
&mpss_mem {
/* Firmware for grandprimelte needs more space */
reg = <0x0 0x86800000 0x0 0x5400000>;
};
&muic_sm5502 {
status = "okay";
};
&usb {
extcon = <&muic_sm5502>, <&muic_sm5502>;
status = "okay";
};
&usb_hs_phy {
extcon = <&muic_sm5502>;
};
Annotation
- Immediate include surface: `msm8916-samsung-fortuna-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.