arch/arm64/boot/dts/freescale/imx8mp-msc-sm2s-14N0600E.dtsi
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/freescale/imx8mp-msc-sm2s-14N0600E.dtsi
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/freescale/imx8mp-msc-sm2s-14N0600E.dtsi- Extension
.dtsi- Size
- 876 bytes
- Lines
- 69
- 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
imx8mp-msc-sm2s.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
/*
* Copyright (C) 2022 Avnet Embedded GmbH
*/
/dts-v1/;
#include "imx8mp-msc-sm2s.dtsi"
/ {
memory@40000000 {
device_type = "memory";
reg = <0x0 0x40000000 0 0x80000000>; /* bank0, 2GiB */
};
};
&cpu_alert0 {
temperature = <95000>;
};
&cpu_crit0 {
temperature = <105000>;
};
&soc_alert0 {
temperature = <95000>;
};
&soc_crit0 {
temperature = <105000>;
};
&tca6424 {
gbe0-int-hog {
gpio-hog;
input;
gpios = <3 GPIO_ACTIVE_LOW>;
};
gbe1-int-hog {
gpio-hog;
input;
gpios = <4 GPIO_ACTIVE_LOW>;
};
cam2-rst-hog {
gpio-hog;
output-high;
gpios = <9 GPIO_ACTIVE_LOW>;
};
cam2-pwr-hog {
gpio-hog;
output-high;
gpios = <10 GPIO_ACTIVE_LOW>;
};
tpm-int-hog {
gpio-hog;
input;
gpios = <13 GPIO_ACTIVE_LOW>;
};
wifi-int-hog {
gpio-hog;
input;
gpios = <14 GPIO_ACTIVE_LOW>;
};
};
Annotation
- Immediate include surface: `imx8mp-msc-sm2s.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.