arch/arm64/boot/dts/sprd/ums512-1h10.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/sprd/ums512-1h10.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/sprd/ums512-1h10.dts- Extension
.dts- Size
- 945 bytes
- Lines
- 62
- 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
ums512.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)
/*
* Unisoc UMS512-1h10 boards DTS file
*
* Copyright (C) 2021, Unisoc Inc.
*/
/dts-v1/;
#include "ums512.dtsi"
/ {
model = "Unisoc UMS512-1H10 Board";
compatible = "sprd,ums512-1h10", "sprd,ums512";
aliases {
serial0 = &uart0;
serial1 = &uart1;
};
memory@80000000 {
device_type = "memory";
reg = <0x0 0x80000000 0x0 0x80000000>;
};
chosen {
stdout-path = "serial1:115200n8";
};
};
&uart0 {
status = "okay";
};
&uart1 {
status = "okay";
};
/* SD card */
&sdio0 {
bus-width = <4>;
no-sdio;
no-mmc;
sprd,phy-delay-sd-uhs-sdr104 = <0x7f 0x73 0x72 0x72>;
sprd,phy-delay-sd-uhs-sdr50 = <0x6e 0x7f 0x01 0x01>;
sprd,phy-delay-sd-highspeed = <0x7f 0x1a 0x9a 0x9a>;
sprd,phy-delay-legacy = <0x7f 0x1a 0x9a 0x9a>;
sd-uhs-sdr104;
sd-uhs-sdr50;
};
/* EMMC storage */
&sdio3 {
status = "okay";
bus-width = <8>;
no-sdio;
no-sd;
non-removable;
cap-mmc-hw-reset;
};
Annotation
- Immediate include surface: `ums512.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.