arch/arm64/boot/dts/freescale/fsl-lx2160a-tqmlx2160a-mblx2160a_x_11_x.dtso

File Facts

System

Linux kernel

Corpus path

arch/arm64/boot/dts/freescale/fsl-lx2160a-tqmlx2160a-mblx2160a_x_11_x.dtso

Extension

.dtso

Size

773 bytes

Lines

50

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

• 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 (c) 2020-2023 TQ-Systems GmbH <linux@ew.tq-group.com>,
 * D-82229 Seefeld, Germany.
 * Author: Gregor Herburger
 */

/dts-v1/;
/plugin/;

&dpmac12 {
	phy-handle = <&dp83867_1_1>;
	phy-connection-type = "sgmii";
	managed = "in-band-status";
};

&dpmac13 {
	phy-handle = <&dp83867_1_5>;
	phy-connection-type = "sgmii";
	managed = "in-band-status";
};

&dpmac14 {
	phy-handle = <&dp83867_1_6>;
	phy-connection-type = "sgmii";
	managed = "in-band-status";
};

&dpmac16 {
	phy-handle = <&dp83867_1_4>;
	phy-connection-type = "sgmii";
	managed = "in-band-status";
};

&pcs_mdio12 {
	status = "okay";
};

&pcs_mdio13 {
	status = "okay";
};

&pcs_mdio14 {
	status = "okay";
};

&pcs_mdio16 {
	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.