arch/arm64/boot/dts/freescale/tqmls1088a-mbls10xxa-mc.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/freescale/tqmls1088a-mbls10xxa-mc.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/freescale/tqmls1088a-mbls10xxa-mc.dtsi- Extension
.dtsi- Size
- 2191 bytes
- Lines
- 131
- 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
dt-bindings/net/ti-dp83867.h
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) 2018-2023 TQ-Systems GmbH <linux@ew.tq-group.com>,
* D-82229 Seefeld, Germany.
* Author: Gregor Herburger, Timo Herbrecher
*
* Device Tree Include file for MBLS10xxA from TQ (MC related sections)
*/
#include <dt-bindings/net/ti-dp83867.h>
/ {
};
&dpmac1 {
pcs-handle = <&pcs1>;
};
&dpmac2 {
pcs-handle = <&pcs2>;
};
&dpmac3 {
pcs-handle = <&pcs3_0>;
};
&dpmac4 {
pcs-handle = <&pcs3_1>;
};
&dpmac5 {
pcs-handle = <&pcs3_2>;
};
&dpmac6 {
pcs-handle = <&pcs3_3>;
};
&dpmac7 {
pcs-handle = <&pcs7_0>;
};
&dpmac8 {
pcs-handle = <&pcs7_1>;
};
&dpmac9 {
pcs-handle = <&pcs7_2>;
};
&dpmac10 {
pcs-handle = <&pcs7_3>;
};
&emdio1 {
status = "okay";
qsgmii2_phy1: ethernet-phy@0 {
compatible = "ethernet-phy-ieee802.3-c22";
reg = <0x00>;
};
qsgmii2_phy2: ethernet-phy@1 {
compatible = "ethernet-phy-ieee802.3-c22";
reg = <0x01>;
};
qsgmii2_phy3: ethernet-phy@2 {
compatible = "ethernet-phy-ieee802.3-c22";
Annotation
- Immediate include surface: `dt-bindings/net/ti-dp83867.h`.
- 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.