arch/arm/boot/dts/broadcom/bcm953012er.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/broadcom/bcm953012er.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/broadcom/bcm953012er.dts- Extension
.dts- Size
- 2560 bytes
- Lines
- 101
- 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
bcm4708.dtsibcm5301x-nand-cs0-bch8.dtsi
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
/dts-v1/;
#include "bcm4708.dtsi"
#include "bcm5301x-nand-cs0-bch8.dtsi"
/ {
model = "NorthStar Enterprise Router (BCM953012ER)";
compatible = "brcm,bcm953012er", "brcm,bcm53012", "brcm,bcm4708";
memory@0 {
device_type = "memory";
reg = <0x00000000 0x8000000>;
};
gpio-keys {
compatible = "gpio-keys";
button-wps {
label = "WPS";
linux,code = <KEY_WPS_BUTTON>;
gpios = <&chipcommon 6 GPIO_ACTIVE_LOW>;
};
button-restart {
label = "Reset";
linux,code = <KEY_RESTART>;
gpios = <&chipcommon 15 GPIO_ACTIVE_LOW>;
};
};
};
&spi_nor {
status = "okay";
};
&srab {
status = "okay";
ports {
port@0 {
reg = <0>;
label = "port0";
};
port@1 {
reg = <1>;
label = "port1";
};
port@5 {
reg = <5>;
label = "cpu";
ethernet = <&gmac0>;
};
port@7 {
status = "disabled";
};
port@8 {
status = "disabled";
};
};
};
&usb3_phy {
status = "okay";
};
Annotation
- Immediate include surface: `bcm4708.dtsi`, `bcm5301x-nand-cs0-bch8.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.