arch/arm64/boot/dts/amd/elba-asic.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/amd/elba-asic.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/amd/elba-asic.dts- Extension
.dts- Size
- 523 bytes
- Lines
- 29
- 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
elba.dtsielba-16core.dtsielba-asic-common.dtsielba-flash-parts.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-only OR BSD-2-Clause)
/*
* Device Tree file for AMD Pensando Elba Board.
*
* Copyright 2020-2022 Advanced Micro Devices, Inc.
*/
/dts-v1/;
#include "elba.dtsi"
#include "elba-16core.dtsi"
#include "elba-asic-common.dtsi"
#include "elba-flash-parts.dtsi"
/ {
model = "AMD Pensando Elba Board";
compatible = "amd,pensando-elba-ortano", "amd,pensando-elba";
aliases {
serial0 = &uart0;
spi0 = &spi0;
spi1 = &qspi;
};
chosen {
stdout-path = "serial0:115200n8";
};
};
Annotation
- Immediate include surface: `elba.dtsi`, `elba-16core.dtsi`, `elba-asic-common.dtsi`, `elba-flash-parts.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.