arch/arm64/boot/dts/freescale/imx8mn-vhip4-evalboard-v2-overlay-ksz8794.dtso
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/freescale/imx8mn-vhip4-evalboard-v2-overlay-ksz8794.dtso
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/freescale/imx8mn-vhip4-evalboard-v2-overlay-ksz8794.dtso- Extension
.dtso- Size
- 529 bytes
- Lines
- 25
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- Inferred role
- Architecture Layer: arch/arm64
- 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
dt-bindings/gpio/gpio.himx8mn-pinfunc.himx8mn-vhip4-evalboard-ksz8794-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+ OR MIT)
/*
* Copyright (C) 2021 Marek Vasut
*/
/dts-v1/;
/plugin/;
#include <dt-bindings/gpio/gpio.h>
#include "imx8mn-pinfunc.h"
&pinctrl_ecspi1 {
fsl,pins = <
MX8MN_IOMUXC_ECSPI1_SCLK_ECSPI1_SCLK 0x10
MX8MN_IOMUXC_ECSPI1_MOSI_ECSPI1_MOSI 0x10
MX8MN_IOMUXC_ECSPI1_MISO_ECSPI1_MISO 0x90
/* KS8794 nCS */
MX8MN_IOMUXC_GPIO1_IO11_GPIO1_IO11 0x150
/* ANV32C81 nCS */
MX8MN_IOMUXC_ECSPI1_SS0_GPIO5_IO9 0x150
>;
};
#include "imx8mn-vhip4-evalboard-ksz8794-common.dtsi"
Annotation
- Immediate include surface: `dt-bindings/gpio/gpio.h`, `imx8mn-pinfunc.h`, `imx8mn-vhip4-evalboard-ksz8794-common.dtsi`.
- 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.