arch/arm/boot/dts/nxp/imx/imx6ull-colibri-wifi-aster.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/nxp/imx/imx6ull-colibri-wifi-aster.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/nxp/imx/imx6ull-colibri-wifi-aster.dts- Extension
.dts- Size
- 821 bytes
- Lines
- 61
- 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
imx6ull-colibri-wifi.dtsiimx6ull-colibri-aster.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-later OR MIT
/*
* Copyright 2017-2022 Toradex
*/
/dts-v1/;
#include "imx6ull-colibri-wifi.dtsi"
#include "imx6ull-colibri-aster.dtsi"
/ {
model = "Toradex Colibri iMX6ULL 512MB on Colibri Aster";
compatible = "toradex,colibri-imx6ull-wifi-aster",
"toradex,colibri-imx6ull-wifi",
"fsl,imx6ull";
};
&ad7879_ts {
status = "okay";
};
&atmel_mxt_ts {
status = "okay";
};
&backlight {
status = "okay";
};
&i2c1 {
status = "okay";
};
&i2c2 {
status = "okay";
};
&lcdif {
status = "okay";
};
&panel_dpi {
status = "okay";
};
&pwm4 {
status = "okay";
};
/* PWM <B> */
&pwm5 {
/* Pin already used by atmel_mxt_ts touchscreen */
status = "disabled";
};
/* PWM <C> */
&pwm6 {
/* Pin already used by atmel_mxt_ts touchscreen */
status = "disabled";
};
Annotation
- Immediate include surface: `imx6ull-colibri-wifi.dtsi`, `imx6ull-colibri-aster.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.