arch/arm64/boot/dts/freescale/imx8mp-evk-lvds1-imx-dlvds-hdmi-channel0.dtso
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/freescale/imx8mp-evk-lvds1-imx-dlvds-hdmi-channel0.dtso
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/freescale/imx8mp-evk-lvds1-imx-dlvds-hdmi-channel0.dtso- Extension
.dtso- Size
- 648 bytes
- Lines
- 45
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- Inferred role
- Architecture Layer: arch/arm64
- 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
imx8mp-evk-lvds1-imx-lvds-hdmi-common.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)
/*
* Copyright 2024 NXP
*/
#include "imx8mp-evk-lvds1-imx-lvds-hdmi-common.dtsi"
&it6263 {
ports {
port@0 {
reg = <0>;
dual-lvds-even-pixels;
it6263_lvds_link1: endpoint {
remote-endpoint = <&ldb_lvds_ch1>;
};
};
port@1 {
reg = <1>;
dual-lvds-odd-pixels;
it6263_lvds_link2: endpoint {
remote-endpoint = <&ldb_lvds_ch0>;
};
};
};
};
&lvds_bridge {
ports {
port@1 {
ldb_lvds_ch0: endpoint {
remote-endpoint = <&it6263_lvds_link2>;
};
};
port@2 {
ldb_lvds_ch1: endpoint {
remote-endpoint = <&it6263_lvds_link1>;
};
};
};
};
Annotation
- Immediate include surface: `imx8mp-evk-lvds1-imx-lvds-hdmi-common.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.