arch/arm/boot/dts/broadcom/bcm911360_entphn.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/broadcom/bcm911360_entphn.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/broadcom/bcm911360_entphn.dts- Extension
.dts- Size
- 2595 bytes
- Lines
- 100
- 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
bcm-cygnus.dtsidt-bindings/input/input.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
/dts-v1/;
#include "bcm-cygnus.dtsi"
#include "dt-bindings/input/input.h"
/ {
model = "Cygnus Enterprise Phone (BCM911360_ENTPHN)";
compatible = "brcm,bcm11360", "brcm,cygnus";
aliases {
serial0 = &uart3;
};
chosen {
stdout-path = "serial0:115200n8";
};
gpio-keys {
compatible = "gpio-keys";
button-hook {
label = "HOOK";
linux,code = <KEY_O>;
gpios = <&gpio_asiu 48 0>;
};
};
};
ð0 {
status = "okay";
};
&mdio {
status = "okay";
};
&switch {
status = "okay";
};
&v3d {
assigned-clocks =
<&mipipll BCM_CYGNUS_MIPIPLL>,
<&mipipll BCM_CYGNUS_MIPIPLL_CH2_V3D>;
assigned-clock-rates = <525000000>, <300000000>;
status = "okay";
};
&uart3 {
status = "okay";
};
&nand_controller {
nand@1 {
compatible = "brcm,nandcs";
reg = <0>;
nand-on-flash-bbt;
#address-cells = <1>;
#size-cells = <1>;
nand-ecc-strength = <24>;
nand-ecc-step-size = <1024>;
brcm,nand-oob-sector-size = <27>;
};
};
Annotation
- Immediate include surface: `bcm-cygnus.dtsi`, `dt-bindings/input/input.h`.
- 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.