arch/arm/boot/dts/st/stm32mp157c-phyboard-sargas-rdk.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/st/stm32mp157c-phyboard-sargas-rdk.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/st/stm32mp157c-phyboard-sargas-rdk.dts- Extension
.dts- Size
- 669 bytes
- Lines
- 43
- 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.dtsistm32mp15xc.dtsistm32mp15xx-phycore-som.dtsistm32mp15xx-phyboard-sargas.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) Phytec GmbH 2019-2020 - All Rights Reserved
* Author: Dom VOVARD <dom.vovard@linrt.com>.
*/
/dts-v1/;
#include "stm32mp157.dtsi"
#include "stm32mp15xc.dtsi"
#include "stm32mp15xx-phycore-som.dtsi"
#include "stm32mp15xx-phyboard-sargas.dtsi"
/ {
model = "PHYTEC phyBOARD-Sargas STM32MP157C";
compatible = "phytec,phycore-stm32mp1-3",
"phytec,phycore-stm32mp157c-som", "st,stm32mp157";
};
&cryp1 {
status = "okay";
};
&gpu {
status = "okay";
};
&i2c4_eeprom {
status = "okay";
};
&i2c4_rtc {
status = "okay";
};
&qspi {
status = "okay";
};
&sdmmc2 {
status = "okay";
};
Annotation
- Immediate include surface: `stm32mp157.dtsi`, `stm32mp15xc.dtsi`, `stm32mp15xx-phycore-som.dtsi`, `stm32mp15xx-phyboard-sargas.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.