arch/arm/boot/dts/broadcom/bcm2835-rpi-common.dtsi

File Facts

System

Linux kernel

Corpus path

arch/arm/boot/dts/broadcom/bcm2835-rpi-common.dtsi

Extension

.dtsi

Size

700 bytes

Lines

32

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/power/raspberrypi-power.h

Detected Declarations

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

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0
/*
 * This include file covers the common peripherals and configuration between
 * bcm2835, bcm2836 and bcm2837 implementations that interact with RPi's
 * firmware interface.
 */

#include <dt-bindings/power/raspberrypi-power.h>

&hdmi {
	clocks = <&firmware_clocks 9>,
		 <&firmware_clocks 13>;
	clock-names = "pixel", "hdmi";
};

&pm {
	clocks = <&firmware_clocks 5>,
		 <&clocks BCM2835_CLOCK_PERI_IMAGE>,
		 <&clocks BCM2835_CLOCK_H264>,
		 <&clocks BCM2835_CLOCK_ISP>;
	clock-names = "v3d", "peri_image", "h264", "isp";
};

&v3d {
	clocks = <&firmware_clocks 5>;
	power-domains = <&power RPI_POWER_DOMAIN_V3D>;
};

&vec {
	clocks = <&firmware_clocks 15>;
};

Annotation

• Immediate include surface: `dt-bindings/power/raspberrypi-power.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.