arch/arm/boot/dts/nxp/imx/imx6q-skov-revc-lt2.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/nxp/imx/imx6q-skov-revc-lt2.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/nxp/imx/imx6q-skov-revc-lt2.dts- Extension
.dts- Size
- 766 bytes
- Lines
- 38
- Domain
- Architecture Layer
- Bucket
- arch/arm
- 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
imx6q.dtsiimx6qdl-skov-cpu.dtsiimx6qdl-skov-cpu-revc.dtsiimx6qdl-skov-revc-lt2.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 (C) 2020 Pengutronix, Ulrich Oelmann <kernel@pengutronix.de>
/dts-v1/;
#include "imx6q.dtsi"
#include "imx6qdl-skov-cpu.dtsi"
#include "imx6qdl-skov-cpu-revc.dtsi"
#include "imx6qdl-skov-revc-lt2.dtsi"
/ {
model = "SKOV IMX6 CPU QuadCore";
compatible = "skov,imx6q-skov-revc-lt2", "fsl,imx6q";
};
&hdmi {
ddc-i2c-bus = <&i2c2>;
status = "okay";
};
&i2c2 {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_i2c2>;
clock-frequency = <100000>;
status = "okay";
};
&iomuxc {
pinctrl_i2c2: i2c2grp {
fsl,pins = <
/* internal 22 k pull up required */
MX6QDL_PAD_KEY_COL3__I2C2_SCL 0x4001f878
/* internal 22 k pull up required */
MX6QDL_PAD_KEY_ROW3__I2C2_SDA 0x4001f878
>;
};
};
Annotation
- Immediate include surface: `imx6q.dtsi`, `imx6qdl-skov-cpu.dtsi`, `imx6qdl-skov-cpu-revc.dtsi`, `imx6qdl-skov-revc-lt2.dtsi`.
- Atlas domain: Architecture Layer / arch/arm.
- 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.