arch/arm/boot/dts/microchip/mpa1600.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/microchip/mpa1600.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/microchip/mpa1600.dts- Extension
.dts- Size
- 1183 bytes
- Lines
- 80
- 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
at91rm9200.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
/*
* mpa1600.dts - Device Tree file for Phontech MPA 1600
*
* Copyright (C) 2013 Joachim Eastwood <manabian@gmail.com>
*/
/dts-v1/;
#include "at91rm9200.dtsi"
/ {
model = "Phontech MPA 1600";
compatible = "phontech,mpa1600", "atmel,at91rm9200";
memory@20000000 {
reg = <0x20000000 0x4000000>;
};
clocks {
slow_xtal {
clock-frequency = <32768>;
};
main_xtal {
clock-frequency = <18432000>;
};
};
ahb {
apb {
dbgu: serial@fffff200 {
status = "okay";
};
tcb0: timer@fffa0000 {
timer@0 {
compatible = "atmel,tcb-timer";
reg = <0>, <1>;
};
timer@2 {
compatible = "atmel,tcb-timer";
reg = <2>;
};
};
macb0: ethernet@fffbc000 {
phy-mode = "rmii";
status = "okay";
};
ssc0: ssc@fffd0000 {
status = "okay";
};
ssc1: ssc@fffd4000 {
status = "okay";
};
};
usb0: usb@300000 {
num-ports = <1>;
status = "okay";
};
};
i2c-gpio-0 {
status = "okay";
};
gpio_keys {
Annotation
- Immediate include surface: `at91rm9200.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.