arch/arm/boot/dts/st/stm32mp151a-prtt1a.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/st/stm32mp151a-prtt1a.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/st/stm32mp151a-prtt1a.dts- Extension
.dts- Size
- 915 bytes
- Lines
- 49
- 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
stm32mp151a-prtt1l.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) Protonic Holland
* Author: David Jander <david@protonic.nl>
*/
/dts-v1/;
#include "stm32mp151a-prtt1l.dtsi"
/ {
model = "Protonic PRTT1A";
compatible = "prt,prtt1a", "st,stm32mp151";
};
ðernet0 {
phy-handle = <&phy0>;
};
&mdio0 {
/* TI DP83TD510E */
phy0: ethernet-phy@0 {
compatible = "ethernet-phy-id2000.0181";
reg = <0>;
interrupts-extended = <&gpioa 4 IRQ_TYPE_LEVEL_LOW>;
reset-gpios = <&gpioa 3 GPIO_ACTIVE_LOW>;
reset-assert-us = <10>;
reset-deassert-us = <35>;
};
};
&{pwm5_pins_a/pins} {
pinmux = <STM32_PINMUX('A', 0, AF2)>; /* TIM5_CH1 */
};
&{pwm5_sleep_pins_a/pins} {
pinmux = <STM32_PINMUX('A', 0, ANALOG)>; /* TIM5_CH1 */
};
&timers5 {
status = "okay";
pwm {
pinctrl-0 = <&pwm5_pins_a>;
pinctrl-1 = <&pwm5_sleep_pins_a>;
pinctrl-names = "default", "sleep";
status = "okay";
};
};
Annotation
- Immediate include surface: `stm32mp151a-prtt1l.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.