arch/arm/boot/dts/marvell/kirkwood-ds212.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/marvell/kirkwood-ds212.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/marvell/kirkwood-ds212.dts- Extension
.dts- Size
- 795 bytes
- Lines
- 47
- 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
kirkwood.dtsikirkwood-6282.dtsikirkwood-synology.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
/*
* Andrew Lunn <andrew@lunn.ch>
* Ben Peddell <klightspeed@killerwolves.net>
*
*/
/dts-v1/;
#include "kirkwood.dtsi"
#include "kirkwood-6282.dtsi"
#include "kirkwood-synology.dtsi"
/ {
model = "Synology DS212, DS212p v10, v20, DS213air v10, DS213 v10";
compatible = "synology,ds212", "synology,ds212pv10",
"synology,ds212pv10", "synology,ds212pv20",
"synology,ds213airv10", "synology,ds213v10",
"marvell,kirkwood";
memory {
device_type = "memory";
reg = <0x00000000 0x8000000>;
};
chosen {
bootargs = "console=ttyS0,115200n8";
stdout-path = &uart0;
};
gpio-fan-100-15-35-1 {
status = "okay";
};
gpio-leds-hdd-21-2 {
status = "okay";
};
};
&s35390a {
status = "okay";
};
&pcie1 {
status = "okay";
};
Annotation
- Immediate include surface: `kirkwood.dtsi`, `kirkwood-6282.dtsi`, `kirkwood-synology.dtsi`.
- 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.