arch/arm/boot/dts/allwinner/sun7i-a20-linutronix-testbox-v2.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/allwinner/sun7i-a20-linutronix-testbox-v2.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/allwinner/sun7i-a20-linutronix-testbox-v2.dts- Extension
.dts- Size
- 816 bytes
- Lines
- 48
- 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
sun7i-a20-lamobo-r1.dts
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0-or-later
/*
* Copyright 2020 Linutronix GmbH
* Author: Benedikt Spranger <b.spranger@linutronix.de>
*/
/dts-v1/;
#include "sun7i-a20-lamobo-r1.dts"
/ {
model = "Lamobo R1";
compatible = "linutronix,testbox-v2", "lamobo,lamobo-r1", "allwinner,sun7i-a20";
leds {
led-opto1 {
label = "lamobo_r1:opto:powerswitch";
gpios = <&pio 7 3 GPIO_ACTIVE_HIGH>;
};
led-opto2 {
label = "lamobo_r1:opto:relay";
gpios = <&pio 7 5 GPIO_ACTIVE_HIGH>;
};
};
};
&i2c2 {
clock-frequency = <100000>;
status = "okay";
eeprom: eeprom@50 {
compatible = "atmel,24c08";
reg = <0x50>;
status = "okay";
};
atecc508a@60 {
compatible = "atmel,atecc508a";
reg = <0x60>;
};
};
&can0 {
pinctrl-names = "default";
pinctrl-0 = <&can_ph_pins>;
status = "okay";
};
Annotation
- Immediate include surface: `sun7i-a20-lamobo-r1.dts`.
- 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.