arch/arm64/boot/dts/freescale/fsl-ls1088a-tqmls1088a.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/freescale/fsl-ls1088a-tqmls1088a.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/freescale/fsl-ls1088a-tqmls1088a.dtsi- Extension
.dtsi- Size
- 884 bytes
- Lines
- 43
- 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-ls1088a.dtsitqmls10xxa.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-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 LS1088A based SoM of TQ
*/
#include "fsl-ls1088a.dtsi"
#include "tqmls10xxa.dtsi"
&qspi {
num-cs = <2>;
status = "okay";
qflash0: flash@0 {
compatible = "jedec,spi-nor";
reg = <0>;
spi-max-frequency = <62500000>;
spi-rx-bus-width = <4>;
spi-tx-bus-width = <4>;
vcc-supply = <®_vcc1v8>;
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
};
};
qflash1: flash@1 {
compatible = "jedec,spi-nor";
reg = <1>;
#address-cells = <1>;
#size-cells = <1>;
spi-max-frequency = <62500000>;
spi-rx-bus-width = <4>;
spi-tx-bus-width = <4>;
vcc-supply = <®_vcc1v8>;
};
};
Annotation
- Immediate include surface: `fsl-ls1088a.dtsi`, `tqmls10xxa.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.