arch/arm/boot/dts/st/stm32mp157a-dk1.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/st/stm32mp157a-dk1.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/st/stm32mp157a-dk1.dts- Extension
.dts- Size
- 563 bytes
- Lines
- 26
- 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
stm32mp157.dtsistm32mp15-pinctrl.dtsistm32mp15xxac-pinctrl.dtsistm32mp15xx-dkx.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+ OR BSD-3-Clause)
/*
* Copyright (C) STMicroelectronics 2019 - All Rights Reserved
* Author: Alexandre Torgue <alexandre.torgue@st.com> for STMicroelectronics.
*/
/dts-v1/;
#include "stm32mp157.dtsi"
#include "stm32mp15-pinctrl.dtsi"
#include "stm32mp15xxac-pinctrl.dtsi"
#include "stm32mp15xx-dkx.dtsi"
/ {
model = "STMicroelectronics STM32MP157A-DK1 Discovery Board";
compatible = "st,stm32mp157a-dk1", "st,stm32mp157";
aliases {
ethernet0 = ðernet0;
};
chosen {
stdout-path = "serial0:115200n8";
};
};
Annotation
- Immediate include surface: `stm32mp157.dtsi`, `stm32mp15-pinctrl.dtsi`, `stm32mp15xxac-pinctrl.dtsi`, `stm32mp15xx-dkx.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.