arch/arm/boot/dts/allwinner/sun8i-orangepi-zero-interface-board.dtso

File Facts

System

Linux kernel

Corpus path

arch/arm/boot/dts/allwinner/sun8i-orangepi-zero-interface-board.dtso

Extension

.dtso

Size

745 bytes

Lines

47

Domain

Architecture Layer

Bucket

arch/arm

Inferred role

Architecture Layer: arch/arm

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

• No C-style include directives detected by the generator.

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-later OR X11)
/*
 * Copyright (C) 2025 J. Neuschäfer <j.ne@posteo.net>
 *
 * Devicetree overlay for the Orange Pi Zero Interface board (OP0014).
 *
 *   https://orangepi.com/index.php?route=product/product&product_id=871
 *
 * This overlay applies to the following base files:
 *
 * - arch/arm/boot/dts/allwinner/sun8i-h2-plus-orangepi-zero.dts
 * - arch/arm/boot/dts/allwinner/sun8i-h3-orangepi-zero-plus2.dts
 */

/dts-v1/;
/plugin/;

&codec {
	status = "okay";
};

&de {
	status = "okay";
};

&ehci2 {
	status = "okay";
};

&ehci3 {
	status = "okay";
};

&ir {
	pinctrl-names = "default";
	pinctrl-0 = <&r_ir_rx_pin>;
	status = "okay";
};

&ohci2 {
	status = "okay";
};

&ohci3 {
	status = "okay";
};

Annotation

• 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.