arch/arm64/boot/dts/freescale/imx8mp-aipstz.h
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/freescale/imx8mp-aipstz.h
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/freescale/imx8mp-aipstz.h- Extension
.h- Size
- 969 bytes
- Lines
- 34
- Domain
- Architecture Layer
- Bucket
- arch/arm64
- Inferred role
- Architecture Layer: implementation source
- Status
- source implementation candidate
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
#ifndef __IMX8MP_AIPSTZ_H
#define __IMX8MP_AIPSTZ_H
/* consumer type - master or peripheral */
#define IMX8MP_AIPSTZ_MASTER 0x0
#define IMX8MP_AIPSTZ_PERIPH 0x1
/* master configuration options */
#define IMX8MP_AIPSTZ_MPL (1 << 0)
#define IMX8MP_AIPSTZ_MTW (1 << 1)
#define IMX8MP_AIPSTZ_MTR (1 << 2)
#define IMX8MP_AIPSTZ_MBW (1 << 3)
/* peripheral configuration options */
#define IMX8MP_AIPSTZ_TP (1 << 0)
#define IMX8MP_AIPSTZ_WP (1 << 1)
#define IMX8MP_AIPSTZ_SP (1 << 2)
#define IMX8MP_AIPSTZ_BW (1 << 3)
/* master ID definitions */
#define IMX8MP_AIPSTZ_EDMA 0 /* AUDIOMIX EDMA */
#define IMX8MP_AIPSTZ_CA53 1 /* Cortex-A53 cluster */
#define IMX8MP_AIPSTZ_SDMA2 3 /* AUDIOMIX SDMA2 */
#define IMX8MP_AIPSTZ_SDMA3 3 /* AUDIOMIX SDMA3 */
#define IMX8MP_AIPSTZ_HIFI4 5 /* HIFI4 DSP */
#define IMX8MP_AIPSTZ_CM7 6 /* Cortex-M7 */
#endif /* __IMX8MP_AIPSTZ_H */Annotation
- Atlas domain: Architecture Layer / arch/arm64.
- Implementation status: source implementation candidate.
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.