arch/arm64/boot/dts/allwinner/sun50i-a64-pine64-plus.dts

File Facts

System

Linux kernel

Corpus path

arch/arm64/boot/dts/allwinner/sun50i-a64-pine64-plus.dts

Extension

.dts

Size

708 bytes

Lines

36

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

• sun50i-a64-pine64.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+ OR MIT)
// Copyright (c) 2016 ARM Ltd.

#include "sun50i-a64-pine64.dts"

/ {
	model = "Pine64 PINE A64+";
	compatible = "pine64,pine64-plus", "allwinner,sun50i-a64";

	/* TODO: Camera, touchscreen, etc. */
};

&emac {
	pinctrl-names = "default";
	pinctrl-0 = <&rgmii_pins>;
	phy-mode = "rgmii-txid";
	phy-handle = <&ext_rgmii_phy>;
	status = "okay";
};

&mdio {
	ext_rgmii_phy: ethernet-phy@1 {
		compatible = "ethernet-phy-ieee802.3-c22";
		reg = <1>;
	};
};

&reg_dc1sw {
	/*
	 * Ethernet PHY needs 30ms to properly power up and some more
	 * to initialize. 100ms should be plenty of time to finish
	 * whole process.
	 */
	regulator-enable-ramp-delay = <100000>;
};

Annotation

• Immediate include surface: `sun50i-a64-pine64.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.