arch/arm/boot/dts/nxp/imx/imx6qp-yapp4-pegasus-plus.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/nxp/imx/imx6qp-yapp4-pegasus-plus.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/nxp/imx/imx6qp-yapp4-pegasus-plus.dts- Extension
.dts- Size
- 768 bytes
- Lines
- 67
- 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
imx6qp.dtsiimx6dl-yapp43-common.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
//
// Copyright (C) 2021 Y Soft Corporation, a.s.
/dts-v1/;
#include "imx6qp.dtsi"
#include "imx6dl-yapp43-common.dtsi"
/ {
model = "Y Soft IOTA Pegasus+ i.MX6QuadPlus board";
compatible = "ysoft,imx6qp-yapp4-pegasus-plus", "fsl,imx6qp";
memory@10000000 {
device_type = "memory";
reg = <0x10000000 0xf0000000>;
};
};
&beeper {
status = "okay";
};
&gpio_oled {
status = "okay";
};
&i2c3 {
status = "okay";
};
&leds {
status = "okay";
};
&oled_1305 {
status = "okay";
};
&oled_1309 {
status = "okay";
};
&pwm3 {
status = "okay";
};
®_pu {
regulator-always-on;
};
®_usb_h1_vbus {
status = "okay";
};
&touchkeys {
status = "okay";
};
&usbh1 {
status = "okay";
};
&usbphy2 {
status = "okay";
};
Annotation
- Immediate include surface: `imx6qp.dtsi`, `imx6dl-yapp43-common.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.