arch/arm64/boot/dts/qcom/msm8992.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/qcom/msm8992.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/qcom/msm8992.dtsi- Extension
.dtsi- Size
- 1004 bytes
- Lines
- 50
- 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
msm8994.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
/*
* Copyright (c) 2013-2016, The Linux Foundation. All rights reserved.
*/
#include "msm8994.dtsi"
/* 8992 only features 2 A57 cores. */
/delete-node/ &cpu6;
/delete-node/ &cpu7;
/delete-node/ &cpu6_map;
/delete-node/ &cpu7_map;
&gcc {
compatible = "qcom,gcc-msm8992";
};
&mmcc {
compatible = "qcom,mmcc-msm8992";
assigned-clock-rates = <800000000>,
<808000000>,
<1020000000>,
<960000000>,
<800000000>;
};
&ocmem {
reg = <0xfdd00000 0x2000>, <0xfec00000 0x100000>;
gmu-sram@0 {
reg = <0x0 0x80000>;
};
};
&rpmcc {
compatible = "qcom,rpmcc-msm8992", "qcom,rpmcc";
};
&timer {
interrupts = <GIC_PPI 2 (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>,
<GIC_PPI 3 (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>,
<GIC_PPI 4 (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>,
<GIC_PPI 1 (GIC_CPU_MASK_SIMPLE(4) | IRQ_TYPE_LEVEL_LOW)>;
};
&tlmm {
compatible = "qcom,msm8992-pinctrl";
};
Annotation
- Immediate include surface: `msm8994.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.