arch/arm64/boot/dts/freescale/fsl-lx2160a-bluebox3-rev-a.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/freescale/fsl-lx2160a-bluebox3-rev-a.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/freescale/fsl-lx2160a-bluebox3-rev-a.dts- Extension
.dts- Size
- 694 bytes
- Lines
- 35
- 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
fsl-lx2160a-bluebox3.dts
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)
//
// Device Tree file for LX2160A BLUEBOX3
//
// Copyright 2020-2021 NXP
/dts-v1/;
#include "fsl-lx2160a-bluebox3.dts"
/ {
compatible = "fsl,lx2160a-bluebox3-rev-a", "fsl,lx2160a";
};
/* The RGMII PHYs have a different MDIO address */
&emdio1 {
/delete-node/ ethernet-phy@5;
sw1_mii3_phy: ethernet-phy@1 {
/* AR8035 */
compatible = "ethernet-phy-id004d.d072";
reg = <0x1>;
interrupts-extended = <&extirq 6 IRQ_TYPE_LEVEL_LOW>;
};
/delete-node/ ethernet-phy@6;
sw2_mii3_phy: ethernet-phy@2 {
/* AR8035 */
compatible = "ethernet-phy-id004d.d072";
reg = <0x2>;
interrupts-extended = <&extirq 7 IRQ_TYPE_LEVEL_LOW>;
};
};
Annotation
- Immediate include surface: `fsl-lx2160a-bluebox3.dts`.
- 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.