arch/arm64/boot/dts/freescale/imx8qm-ss-img.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/freescale/imx8qm-ss-img.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/freescale/imx8qm-ss-img.dtsi- Extension
.dtsi- Size
- 1189 bytes
- Lines
- 92
- 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
- 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+
/*
* Copyright 2021 NXP
*/
&isi {
compatible = "fsl,imx8qm-isi";
ports {
#address-cells = <1>;
#size-cells = <0>;
port@2 {
reg = <2>;
isi_in_2: endpoint {
remote-endpoint = <&mipi_csi0_out>;
};
};
port@3 {
reg = <3>;
isi_in_3: endpoint {
remote-endpoint = <&mipi_csi1_out>;
};
};
};
};
&jpegdec {
compatible = "nxp,imx8qm-jpgdec", "nxp,imx8qxp-jpgdec";
};
&jpegenc {
compatible = "nxp,imx8qm-jpgenc", "nxp,imx8qxp-jpgenc";
};
&mipi_csi_0 {
compatible = "fsl,imx8qm-mipi-csi2", "fsl,imx8qxp-mipi-csi2";
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
};
port@1 {
reg = <1>;
mipi_csi0_out: endpoint {
remote-endpoint = <&isi_in_2>;
};
};
};
};
&mipi_csi_1 {
compatible = "fsl,imx8qm-mipi-csi2", "fsl,imx8qxp-mipi-csi2";
ports {
#address-cells = <1>;
#size-cells = <0>;
port@0 {
reg = <0>;
};
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.