arch/arm64/boot/dts/rockchip/rk3326-anbernic-rg351v.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/rockchip/rk3326-anbernic-rg351v.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/rockchip/rk3326-anbernic-rg351v.dts- Extension
.dts- Size
- 817 bytes
- Lines
- 45
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- 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
rk3326-anbernic-rg351m.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)
/dts-v1/;
#include "rk3326-anbernic-rg351m.dtsi"
/ {
model = "Anbernic RG351V";
compatible = "anbernic,rg351v", "rockchip,rk3326";
gpio_keys_vol: gpio-keys-vol {
compatible = "gpio-keys";
autorepeat;
button-vol-down {
gpios = <&gpio2 RK_PA1 GPIO_ACTIVE_LOW>;
label = "VOLUMEDOWN";
linux,code = <KEY_VOLUMEDOWN>;
};
button-vol-up {
gpios = <&gpio2 RK_PA0 GPIO_ACTIVE_LOW>;
label = "VOLUMEUP";
linux,code = <KEY_VOLUMEUP>;
};
};
};
&internal_display {
compatible = "anbernic,rg351v-panel", "newvision,nv3051d";
vdd-supply = <&vcc_lcd>;
};
&io_domains {
vccio1-supply = <&vccio_sd>;
};
&vcc_sd {
regulator-max-microvolt = <3000000>;
regulator-min-microvolt = <1800000>;
};
&vccio_sd {
regulator-max-microvolt = <1800000>;
};
Annotation
- Immediate include surface: `rk3326-anbernic-rg351m.dtsi`.
- Atlas domain: Architecture Layer / arch/arm64.
- 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.