arch/arm64/boot/dts/xilinx/versal-net.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/xilinx/versal-net.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/xilinx/versal-net.dtsi- Extension
.dtsi- Size
- 29636 bytes
- Lines
- 1161
- 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
- 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
/*
* dts file for Xilinx Versal NET
*
* (C) Copyright 2022, Xilinx, Inc.
* (C) Copyright 2022 - 2025, Advanced Micro Devices, Inc.
*
* Michal Simek <michal.simek@amd.com>
*/
/dts-v1/;
/ {
compatible = "xlnx,versal-net";
model = "Xilinx Versal NET";
#address-cells = <2>;
#size-cells = <2>;
interrupt-parent = <&gic>;
options {
u-boot {
compatible = "u-boot,config";
bootscr-address = /bits/ 64 <0x20000000>;
};
};
cpus {
#address-cells = <1>;
#size-cells = <0>;
cpu-map {
cluster0 {
core0 {
cpu = <&cpu0>;
};
core1 {
cpu = <&cpu100>;
};
core2 {
cpu = <&cpu200>;
};
core3 {
cpu = <&cpu300>;
};
};
cluster1 {
core0 {
cpu = <&cpu10000>;
};
core1 {
cpu = <&cpu10100>;
};
core2 {
cpu = <&cpu10200>;
};
core3 {
cpu = <&cpu10300>;
};
};
cluster2 {
core0 {
cpu = <&cpu20000>;
};
core1 {
cpu = <&cpu20100>;
};
Annotation
- 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.