arch/arm/boot/dts/arm/arm-realview-eb-a9mp.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/arm/arm-realview-eb-a9mp.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/arm/arm-realview-eb-a9mp.dts- Extension
.dts- Size
- 1941 bytes
- Lines
- 71
- 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
arm-realview-eb-mp.dtsi
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
/dts-v1/;
#include "arm-realview-eb-mp.dtsi"
/ {
model = "ARM RealView EB Cortex A9 MPCore";
/*
* This is the Cortex A9 MPCore tile used with the
* RealView EB.
*/
cpus {
#address-cells = <1>;
#size-cells = <0>;
enable-method = "arm,realview-smp";
A9_0: cpu@0 {
device_type = "cpu";
compatible = "arm,cortex-a9";
reg = <0>;
next-level-cache = <&L2>;
};
A9_1: cpu@1 {
device_type = "cpu";
compatible = "arm,cortex-a9";
reg = <1>;
next-level-cache = <&L2>;
};
A9_2: cpu@2 {
device_type = "cpu";
compatible = "arm,cortex-a9";
reg = <2>;
next-level-cache = <&L2>;
};
A9_3: cpu@3 {
device_type = "cpu";
compatible = "arm,cortex-a9";
reg = <3>;
next-level-cache = <&L2>;
};
};
};
&pmu {
interrupt-affinity = <&A9_0>, <&A9_1>, <&A9_2>, <&A9_3>;
};
Annotation
- Immediate include surface: `arm-realview-eb-mp.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.