arch/riscv/boot/dts/allwinner/sun20i-d1-lichee-rv-86-panel-480p.dts
Source file repositories/reference/linux-study-clean/arch/riscv/boot/dts/allwinner/sun20i-d1-lichee-rv-86-panel-480p.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/riscv/boot/dts/allwinner/sun20i-d1-lichee-rv-86-panel-480p.dts- Extension
.dts- Size
- 744 bytes
- Lines
- 30
- 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-lichee-rv-86-panel.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+ OR MIT)
// Copyright (C) 2022 Samuel Holland <samuel@sholland.org>
#include "sun20i-d1-lichee-rv-86-panel.dtsi"
/ {
model = "Sipeed Lichee RV 86 Panel (480p)";
compatible = "sipeed,lichee-rv-86-panel-480p", "sipeed,lichee-rv",
"allwinner,sun20i-d1";
};
&i2c2 {
pinctrl-0 = <&i2c2_pb0_pins>;
pinctrl-names = "default";
status = "okay";
touchscreen@48 {
compatible = "focaltech,ft6236";
reg = <0x48>;
interrupt-parent = <&pio>;
interrupts = <6 14 IRQ_TYPE_LEVEL_LOW>; /* PG14 */
iovcc-supply = <®_vcc_3v3>;
reset-gpios = <&pio 6 15 GPIO_ACTIVE_LOW>; /* PG15 */
touchscreen-size-x = <480>;
touchscreen-size-y = <480>;
vcc-supply = <®_vcc_3v3>;
wakeup-source;
};
};
Annotation
- Immediate include surface: `sun20i-d1-lichee-rv-86-panel.dtsi`.
- 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.