arch/arm64/boot/dts/sophgo/sg2000-milkv-duo-module-01.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/sophgo/sg2000-milkv-duo-module-01.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/sophgo/sg2000-milkv-duo-module-01.dtsi- Extension
.dtsi- Size
- 574 bytes
- Lines
- 41
- 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/pinctrl/pinctrl-sg2000.hsg2000.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)
#include <dt-bindings/pinctrl/pinctrl-sg2000.h>
#include "sg2000.dtsi"
/ {
model = "Milk-V Duo Module 01";
compatible = "milkv,duo-module-01", "sophgo,sg2000";
aliases {
serial0 = &uart0;
serial1 = &uart1;
serial2 = &uart2;
serial3 = &uart3;
serial4 = &uart4;
};
};
&osc {
clock-frequency = <25000000>;
};
&emmc {
bus-width = <4>;
no-1-8-v;
cap-mmc-hw-reset;
no-sd;
no-sdio;
non-removable;
status = "okay";
};
/* Wi-Fi */
&sdhci1 {
bus-width = <4>;
cap-sdio-irq;
no-mmc;
no-sd;
non-removable;
};
Annotation
- Immediate include surface: `dt-bindings/pinctrl/pinctrl-sg2000.h`, `sg2000.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.