arch/arm/boot/dts/marvell/armada-388-clearfog-pro.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/marvell/armada-388-clearfog-pro.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/marvell/armada-388-clearfog-pro.dts- Extension
.dts- Size
- 380 bytes
- Lines
- 15
- Domain
- Architecture Layer
- Bucket
- arch/arm
- 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
armada-388-clearfog.dts
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)
/*
* Device Tree file for SolidRun Clearfog Pro revision A1 rev 2.0 (88F6828)
*
* Copyright (C) 2015 Russell King
*/
#include "armada-388-clearfog.dts"
/ {
model = "SolidRun Clearfog Pro A1";
compatible = "solidrun,clearfog-pro-a1",
"solidrun,clearfog-a1", "marvell,armada388",
"marvell,armada385", "marvell,armada380";
};
Annotation
- Immediate include surface: `armada-388-clearfog.dts`.
- Atlas domain: Architecture Layer / arch/arm.
- 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.