arch/arm/boot/dts/nxp/mxs/Makefile

Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/nxp/mxs/Makefile

File Facts

System: Linux kernel
Corpus path: arch/arm/boot/dts/nxp/mxs/Makefile
Extension: [no extension]
Size: 793 bytes
Lines: 36
Domain: Architecture Layer
Bucket: arch/arm
Inferred role: Architecture Layer: build/configuration rule
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
dtb-$(CONFIG_ARCH_MXS) += \
	imx23-evk.dtb \
	imx23-olinuxino.dtb \
	imx23-sansa.dtb \
	imx23-stmp378x_devb.dtb \
	imx23-xfi3.dtb \
	imx28-amarula-rmm.dtb \
	imx28-apf28.dtb \
	imx28-apf28dev.dtb \
	imx28-apx4devkit.dtb \
	imx28-btt3-0.dtb \
	imx28-btt3-1.dtb \
	imx28-btt3-2.dtb \
	imx28-cfa10036.dtb \
	imx28-cfa10037.dtb \
	imx28-cfa10049.dtb \
	imx28-cfa10055.dtb \
	imx28-cfa10056.dtb \
	imx28-cfa10057.dtb \
	imx28-cfa10058.dtb \
	imx28-duckbill-2-485.dtb \
	imx28-duckbill-2.dtb \
	imx28-duckbill-2-enocean.dtb \
	imx28-duckbill-2-spi.dtb \
	imx28-duckbill.dtb \
	imx28-eukrea-mbmx283lc.dtb \
	imx28-eukrea-mbmx287lc.dtb \
	imx28-evk.dtb \
	imx28-m28cu3.dtb \
	imx28-m28evk.dtb \
	imx28-sps1.dtb \
	imx28-ts4600.dtb \
	imx28-tx28.dtb \
	imx28-xea.dtb

Annotation

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.