arch/arm/boot/dts/nxp/imx/imx6sx-sdb-mqs.dts
Source file repositories/reference/linux-study-clean/arch/arm/boot/dts/nxp/imx/imx6sx-sdb-mqs.dts
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/boot/dts/nxp/imx/imx6sx-sdb-mqs.dts- Extension
.dts- Size
- 733 bytes
- Lines
- 49
- 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
imx6sx-sdb.dts
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 (C) 2014 Freescale Semiconductor, Inc.
#include "imx6sx-sdb.dts"
/ {
sound {
status = "disabled";
};
sound-mqs {
compatible = "fsl,imx6sx-sdb-mqs",
"fsl,imx-audio-mqs";
model = "mqs-audio";
audio-cpu = <&sai1>;
audio-asrc = <&asrc>;
audio-codec = <&mqs>;
};
};
&usdhc2 {
/* pin conflict with mqs*/
status = "disabled";
};
&mqs {
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_mqs>;
clocks = <&clks IMX6SX_CLK_SAI1>;
clock-names = "mclk";
status = "okay";
};
&sai1 {
pinctrl-0 = <>;
status = "okay";
};
&ssi2 {
status = "disabled";
};
&sdma {
gpr = <&gpr>;
/* SDMA event remap for SAI1 */
fsl,sdma-event-remap = <0 15 1>, <0 16 1>;
};
Annotation
- Immediate include surface: `imx6sx-sdb.dts`.
- 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.