arch/arm/boot/dts/qcom/qcom-msm8916-smp.dtsi
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/qcom/qcom-msm8916-smp.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/qcom/qcom-msm8916-smp.dtsi- Extension
.dtsi- Size
- 716 bytes
- Lines
- 63
- 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
- No C-style include directives detected by the generator.
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
/ {
cpus {
cpu@0 {
enable-method = "qcom,msm8916-smp";
};
cpu@1 {
enable-method = "qcom,msm8916-smp";
};
cpu@2 {
enable-method = "qcom,msm8916-smp";
};
cpu@3 {
enable-method = "qcom,msm8916-smp";
};
idle-states {
/delete-property/ entry-method;
};
};
psci {
status = "disabled";
};
};
&cpu_sleep_0 {
compatible = "qcom,idle-state-spc", "arm,idle-state";
};
&cpu0_acc {
status = "okay";
};
&cpu0_saw {
status = "okay";
};
&cpu1_acc {
status = "okay";
};
&cpu1_saw {
status = "okay";
};
&cpu2_acc {
status = "okay";
};
&cpu2_saw {
status = "okay";
};
&cpu3_acc {
status = "okay";
};
&cpu3_saw {
status = "okay";
};
Annotation
- 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.