arch/arm/boot/dts/allwinner/sun6i-a31s-inet-q972.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/allwinner/sun6i-a31s-inet-q972.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/allwinner/sun6i-a31s-inet-q972.dts- Extension
.dts- Size
- 2908 bytes
- Lines
- 99
- 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
sun6i-a31s.dtsisun6i-reference-design-tablet.dtsi
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
/dts-v1/;
#include "sun6i-a31s.dtsi"
#include "sun6i-reference-design-tablet.dtsi"
/ {
model = "iNet Q972 tablet";
compatible = "inet-tek,inet-q972", "allwinner,sun6i-a31s";
};
&ehci1 {
status = "okay";
};
&i2c1 {
status = "okay";
ft5406ee8: touchscreen@38 {
compatible = "edt,edt-ft5406";
reg = <0x38>;
interrupt-parent = <&pio>;
interrupts = <0 3 IRQ_TYPE_LEVEL_HIGH>; /* PA3 */
touchscreen-size-x = <768>;
touchscreen-size-y = <1024>;
touchscreen-swapped-x-y;
};
};
&lradc {
vref-supply = <®_aldo3>;
status = "okay";
button-200 {
label = "Volume Down";
linux,code = <KEY_VOLUMEDOWN>;
channel = <0>;
voltage = <200000>;
};
button-900 {
label = "Volume Up";
linux,code = <KEY_VOLUMEUP>;
channel = <0>;
voltage = <900000>;
};
button-1200 {
label = "Back";
linux,code = <KEY_BACK>;
channel = <0>;
voltage = <1200000>;
};
};
&ohci1 {
status = "okay";
};
Annotation
- Immediate include surface: `sun6i-a31s.dtsi`, `sun6i-reference-design-tablet.dtsi`.
- 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.