arch/arm/boot/dts/marvell/orion5x-linkstation-lsgl.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/marvell/orion5x-linkstation-lsgl.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/marvell/orion5x-linkstation-lsgl.dts- Extension
.dts- Size
- 2893 bytes
- Lines
- 92
- 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
orion5x-linkstation.dtsidt-bindings/gpio/gpio.h
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
/dts-v1/;
#include "orion5x-linkstation.dtsi"
#include <dt-bindings/gpio/gpio.h>
/ {
model = "Buffalo Linkstation Pro/Live";
compatible = "buffalo,lsgl", "marvell,orion5x-88f5182", "marvell,orion5x";
memory { /* 128 MB */
device_type = "memory";
reg = <0x00000000 0x8000000>;
};
};
&pinctrl {
pmx_power_hdd: pmx-power-hdd {
marvell,pins = "mpp1";
marvell,function = "gpio";
};
pmx_power_usb: pmx-power-usb {
marvell,pins = "mpp9";
marvell,function = "gpio";
};
};
&hdd_power {
gpios = <&gpio0 1 GPIO_ACTIVE_HIGH>;
};
&usb_power {
gpios = <&gpio0 9 GPIO_ACTIVE_HIGH>;
};
&sata {
nr-ports = <2>;
};
&ehci1 {
status = "okay";
};
Annotation
- Immediate include surface: `orion5x-linkstation.dtsi`, `dt-bindings/gpio/gpio.h`.
- 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.