arch/arm/boot/dts/nxp/imx/imx6ull-myir-mys-6ulx-eval.dts

File Facts

System

Linux kernel

Corpus path

arch/arm/boot/dts/nxp/imx/imx6ull-myir-mys-6ulx-eval.dts

Extension

.dts

Size

389 bytes

Lines

20

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.dtsi
• imx6ull-myir-mys-6ulx.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) 2020 Linumiz
 * Author: Parthiban Nallathambi <parthiban@linumiz.com>
 */

/dts-v1/;
#include "imx6ull.dtsi"
#include "imx6ull-myir-mys-6ulx.dtsi"

/ {
	model = "MYiR i.MX6ULL MYS-6ULX Single Board Computer with NAND";
	compatible = "myir,imx6ull-mys-6ulx-eval", "fsl,imx6ull";
};

&gpmi {
	fsl,use-minimum-ecc;
	status = "okay";
};

Annotation

• Immediate include surface: `imx6ull.dtsi`, `imx6ull-myir-mys-6ulx.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.