arch/mips/boot/dts/brcm/bcm97346dbsmb.dts
Source file repositories/reference/linux-study-clean/arch/mips/boot/dts/brcm/bcm97346dbsmb.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/mips/boot/dts/brcm/bcm97346dbsmb.dts- Extension
.dts- Size
- 1190 bytes
- Lines
- 125
- Domain
- Architecture Layer
- Bucket
- arch/mips
- 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
bcm7346.dtsibcm97xxx-nand-cs1-bch24.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
/dts-v1/;
#include "bcm7346.dtsi"
#include "bcm97xxx-nand-cs1-bch24.dtsi"
/ {
compatible = "brcm,bcm97346dbsmb", "brcm,bcm7346";
model = "Broadcom BCM97346DBSMB";
memory@0 {
device_type = "memory";
reg = <0x00000000 0x10000000>, <0x20000000 0x30000000>;
};
chosen {
bootargs = "console=ttyS0,115200";
stdout-path = &uart0;
};
};
&uart0 {
status = "okay";
};
&uart1 {
status = "okay";
};
&uart2 {
status = "okay";
};
&bsca {
status = "okay";
};
&bscb {
status = "okay";
};
&bscc {
status = "okay";
};
&bscd {
status = "okay";
};
&bsce {
status = "okay";
};
&pwma {
status = "okay";
};
&pwmb {
status = "okay";
};
&watchdog {
status = "okay";
};
&enet0 {
status = "okay";
};
&ehci0 {
Annotation
- Immediate include surface: `bcm7346.dtsi`, `bcm97xxx-nand-cs1-bch24.dtsi`.
- Atlas domain: Architecture Layer / arch/mips.
- 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.