arch/arm/boot/dts/broadcom/bcm23550-sparrow.dts

File Facts

System

Linux kernel

Corpus path

arch/arm/boot/dts/broadcom/bcm23550-sparrow.dts

Extension

.dts

Size

2337 bytes

Lines

82

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

• dt-bindings/gpio/gpio.h
• bcm23550.dtsi

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

/dts-v1/;

#include <dt-bindings/gpio/gpio.h>

#include "bcm23550.dtsi"

/ {
	model = "BCM23550 Sparrow board";
	compatible = "brcm,bcm23550-sparrow", "brcm,bcm23550";

	chosen {
		stdout-path = "/slaves@3e000000/serial@0:115200n8";
		bootargs = "console=ttyS0,115200n8";
	};

	memory@80000000 {
		device_type = "memory";
		reg = <0x80000000 0x20000000>; /* 512 MB */
	};
};

&uartb {
	status = "okay";
};

&usbotg {
	status = "okay";
};

&usbphy {
	status = "okay";
};

&sdio1 {
	max-frequency = <48000000>;
	status = "okay";
};

&sdio2 {
	non-removable;
	max-frequency = <48000000>;
	status = "okay";
};

&sdio4 {
	max-frequency = <48000000>;
	cd-gpios = <&gpio 91 GPIO_ACTIVE_LOW>;
	status = "okay";
};

Annotation

• Immediate include surface: `dt-bindings/gpio/gpio.h`, `bcm23550.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.