arch/arm/boot/dts/broadcom/bcm2835-rpi-cm1.dtsi
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/broadcom/bcm2835-rpi-cm1.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/broadcom/bcm2835-rpi-cm1.dtsi- Extension
.dtsi- Size
- 844 bytes
- Lines
- 46
- 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
bcm2835.dtsibcm2835-rpi.dtsibcm2835-rpi-common.dtsibcm283x-rpi-led-deprecated.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 "bcm2835.dtsi"
#include "bcm2835-rpi.dtsi"
#include "bcm2835-rpi-common.dtsi"
#include "bcm283x-rpi-led-deprecated.dtsi"
/ {
leds {
led-act {
gpios = <&gpio 47 GPIO_ACTIVE_LOW>;
};
};
memory@0 {
device_type = "memory";
reg = <0 0x20000000>;
};
reg_3v3: fixed-regulator {
compatible = "regulator-fixed";
regulator-name = "3V3";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
regulator-always-on;
};
reg_1v8: fixed-regulator {
compatible = "regulator-fixed";
regulator-name = "1V8";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <1800000>;
regulator-always-on;
};
};
&led_act {
gpios = <&gpio 47 GPIO_ACTIVE_LOW>;
};
&sdhost {
non-removable;
vmmc-supply = <®_3v3>;
vqmmc-supply = <®_1v8>;
};
Annotation
- Immediate include surface: `bcm2835.dtsi`, `bcm2835-rpi.dtsi`, `bcm2835-rpi-common.dtsi`, `bcm283x-rpi-led-deprecated.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.