arch/arm64/boot/dts/freescale/fsl-lx2160a-bluebox3.dts
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/freescale/fsl-lx2160a-bluebox3.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/freescale/fsl-lx2160a-bluebox3.dts- Extension
.dts- Size
- 11250 bytes
- Lines
- 663
- 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.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 OR MIT)
//
// Device Tree file for LX2160A BLUEBOX3
//
// Copyright 2020-2021 NXP
/dts-v1/;
#include "fsl-lx2160a.dtsi"
/ {
model = "NXP Layerscape LX2160ABLUEBOX3";
compatible = "fsl,lx2160a-bluebox3", "fsl,lx2160a";
aliases {
crypto = &crypto;
mmc0 = &esdhc0;
mmc1 = &esdhc1;
serial0 = &uart0;
};
chosen {
stdout-path = "serial0:115200n8";
};
sb_3v3: regulator-sb3v3 {
compatible = "regulator-fixed";
regulator-name = "MC34717-3.3VSB";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
regulator-boot-on;
regulator-always-on;
};
};
&can0 {
status = "okay";
can-transceiver {
max-bitrate = <5000000>;
};
};
&can1 {
status = "okay";
can-transceiver {
max-bitrate = <5000000>;
};
};
&crypto {
status = "okay";
};
&dpmac5 {
phy-handle = <&aqr113c_phy1>;
phy-mode = "usxgmii";
managed = "in-band-status";
};
&dpmac6 {
phy-handle = <&aqr113c_phy2>;
phy-mode = "usxgmii";
managed = "in-band-status";
};
&dpmac9 {
phy-handle = <&aqr113c_phy3>;
phy-mode = "usxgmii";
Annotation
- Immediate include surface: `fsl-lx2160a.dtsi`.
- 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.