arch/riscv/boot/dts/allwinner/sun20i-d1-devterm-v3.14.dts
Source file repositories/reference/linux-study-clean/arch/riscv/boot/dts/allwinner/sun20i-d1-devterm-v3.14.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/riscv/boot/dts/allwinner/sun20i-d1-devterm-v3.14.dts- Extension
.dts- Size
- 946 bytes
- Lines
- 37
- Domain
- Architecture Layer
- Bucket
- arch/riscv
- 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
sun20i-d1-clockworkpi-v3.14.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 MIT)
// Copyright (C) 2022 Samuel Holland <samuel@sholland.org>
#include "sun20i-d1-clockworkpi-v3.14.dts"
/ {
model = "Clockwork DevTerm (R-01)";
compatible = "clockwork,r-01-devterm-v3.14",
"clockwork,r-01-clockworkpi-v3.14",
"allwinner,sun20i-d1";
fan {
compatible = "gpio-fan";
gpios = <&pio 3 10 GPIO_ACTIVE_HIGH>; /* PD10/GPIO41 */
gpio-fan,speed-map = <0 0>,
<6000 1>;
#cooling-cells = <2>;
};
i2c-0 {
compatible = "i2c-gpio";
sda-gpios = <&pio 3 14 (GPIO_ACTIVE_HIGH|GPIO_OPEN_DRAIN)>; /* PD14/GPIO44 */
scl-gpios = <&pio 3 15 (GPIO_ACTIVE_HIGH|GPIO_OPEN_DRAIN)>; /* PD15/GPIO45 */
#address-cells = <1>;
#size-cells = <0>;
adc@54 {
compatible = "ti,adc101c";
reg = <0x54>;
interrupt-parent = <&pio>;
interrupts = <4 12 IRQ_TYPE_LEVEL_LOW>; /* PE12/GPIO35 */
vref-supply = <®_dldo2>;
#io-channel-cells = <1>;
};
};
};
Annotation
- Immediate include surface: `sun20i-d1-clockworkpi-v3.14.dts`.
- Atlas domain: Architecture Layer / arch/riscv.
- 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.