arch/arm/boot/dts/st/stm32mp15xx-dhcom-picoitx-overlay-548-200-x2-mi0700s4t-6.dtso
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/st/stm32mp15xx-dhcom-picoitx-overlay-548-200-x2-mi0700s4t-6.dtso
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/st/stm32mp15xx-dhcom-picoitx-overlay-548-200-x2-mi0700s4t-6.dtso- Extension
.dtso- Size
- 552 bytes
- Lines
- 36
- Domain
- Architecture Layer
- Bucket
- arch/arm
- Inferred role
- Architecture Layer: arch/arm
- 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
stm32mp15xx-dhcom-overlay-panel-dpi.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) 2021 Andreas Geisreiter <ageisreiter@dh-electronics.com>
*/
/dts-v1/;
/plugin/;
#include "stm32mp15xx-dhcom-overlay-panel-dpi.dtsi"
&display_bl {
pwms = <&pwm2 3 10000000 0>;
};
&i2c5 {
#address-cells = <1>;
#size-cells = <0>;
eeprom@50 {
compatible = "atmel,24c04";
reg = <0x50>;
pagesize = <16>;
};
};
<dc_dpi_out {
remote-endpoint = <&panel_in>;
};
&panel {
compatible = "multi-inno,mi0700s4t-6";
};
&panel_in {
remote-endpoint = <<dc_dpi_out>;
};
Annotation
- Immediate include surface: `stm32mp15xx-dhcom-overlay-panel-dpi.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.