arch/arm64/boot/dts/marvell/db-falcon-carrier.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/marvell/db-falcon-carrier.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/marvell/db-falcon-carrier.dtsi- Extension
.dtsi- Size
- 753 bytes
- Lines
- 23
- 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+ OR MIT)
/*
* Copyright (C) 2023 Marvell International Ltd.
*
* Device tree for the Falcon DB Type 7 Com Express carrier board,
* This (DB-98CX8540/80) specific carrier board only maintains
* a PCIe link with the COM Express CPU module, which does not
* require any special DTS definitions.
*
* The board contains the 98CX8540/80 Switch, which connects by
* PCIe to the COM Express CPU module.
* This CPU module can be any standard COM Express CPU module with
* PCIe support.
*
* There is no Linux CPU booting in this mode on the carrier,
* only on the COM Express CPU module.
*/
/ {
model = "Marvell Armada Falcon DB COM EXPRESS type 7 carrier board";
compatible = "marvell,db-falcon-carrier";
};
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.