arch/arm64/boot/dts/freescale/imx8x-colibri-aster.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/freescale/imx8x-colibri-aster.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/freescale/imx8x-colibri-aster.dtsi- Extension
.dtsi- Size
- 967 bytes
- Lines
- 81
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- 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
- No C-style include directives detected by the generator.
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 2018-2021 Toradex
*/
/* Colibri Analogue Inputs */
&adc0 {
status = "okay";
};
/* Colibri PWM_A */
&adma_pwm {
status = "okay";
};
&colibri_gpio_keys {
status = "okay";
};
&extcon_usbc_det {
status = "okay";
};
/* Colibri Ethernet */
&fec1 {
status = "okay";
};
&iomuxc {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_hog0>;
};
/* Colibri SPI */
&lpspi2 {
cs-gpios = <&lsio_gpio1 0 GPIO_ACTIVE_LOW>,
<&lsio_gpio5 2 GPIO_ACTIVE_LOW>;
};
/* Colibri UART_B */
&lpuart0 {
status = "okay";
};
/* Colibri UART_C */
&lpuart2 {
status = "okay";
};
/* Colibri UART_A */
&lpuart3 {
status = "okay";
};
/* USB PHY for usbotg3 */
&usb3_phy {
status = "okay";
};
&usbotg1 {
status = "okay";
};
&usbotg3 {
status = "okay";
};
&usbotg3_cdns3 {
status = "okay";
};
Annotation
- Atlas domain: Architecture Layer / arch/arm64.
- 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.