arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-sp.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-sp.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/allwinner/sun50i-h700-anbernic-rg35xx-sp.dts- Extension
.dts- Size
- 744 bytes
- Lines
- 35
- 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
dt-bindings/input/gpio-keys.hsun50i-h700-anbernic-rg35xx-plus.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-only OR BSD-2-Clause)
/*
* Copyright (C) 2024 Ryan Walklin <ryan@testtoast.com>.
* Copyright (C) 2024 Chris Morgan <macroalpha82@gmail.com>.
*/
#include <dt-bindings/input/gpio-keys.h>
#include "sun50i-h700-anbernic-rg35xx-plus.dts"
/ {
model = "Anbernic RG35XX SP";
compatible = "anbernic,rg35xx-sp", "allwinner,sun50i-h700";
gpio-keys-lid {
compatible = "gpio-keys";
lid-switch {
label = "Lid Switch";
gpios = <&pio 4 7 GPIO_ACTIVE_LOW>; /* PE7 */
linux,can-disable;
linux,code = <SW_LID>;
linux,input-type = <EV_SW>;
wakeup-event-action = <EV_ACT_DEASSERTED>;
wakeup-source;
};
};
};
&r_i2c {
rtc_ext: rtc@51 {
compatible = "nxp,pcf8563";
reg = <0x51>;
};
};
Annotation
- Immediate include surface: `dt-bindings/input/gpio-keys.h`, `sun50i-h700-anbernic-rg35xx-plus.dts`.
- 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.