arch/openrisc/boot/dts/de0-nano-common.dtsi
Source file repositories/reference/linux-study-clean/arch/openrisc/boot/dts/de0-nano-common.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/openrisc/boot/dts/de0-nano-common.dtsi- Extension
.dtsi- Size
- 858 bytes
- Lines
- 43
- Domain
- Architecture Layer
- Bucket
- arch/openrisc
- 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.hdt-bindings/leds/common.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
#include <dt-bindings/gpio/gpio.h>
#include <dt-bindings/leds/common.h>
/ {
leds0: leds {
compatible = "gpio-leds";
led-heartbeat {
gpios = <&gpio0 0 GPIO_ACTIVE_HIGH>;
color = <LED_COLOR_ID_GREEN>;
function = LED_FUNCTION_HEARTBEAT;
linux,default-trigger = "heartbeat";
label = "heartbeat";
};
};
memory@0 {
device_type = "memory";
reg = <0x00000000 0x02000000>;
};
/* 8 Green LEDs */
gpio0: gpio@91000000 {
compatible = "opencores,gpio";
reg = <0x91000000 0x1>, <0x91000001 0x1>;
reg-names = "dat", "dirout";
gpio-controller;
#gpio-cells = <2>;
};
/* 4 DIP Switches */
gpio1: gpio@92000000 {
compatible = "opencores,gpio";
reg = <0x92000000 0x1>, <0x92000001 0x1>;
reg-names = "dat", "dirout";
gpio-controller;
#gpio-cells = <2>;
status = "disabled";
};
};
Annotation
- Immediate include surface: `dt-bindings/gpio/gpio.h`, `dt-bindings/leds/common.h`.
- Atlas domain: Architecture Layer / arch/openrisc.
- 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.