arch/arm64/boot/dts/freescale/imx94-power.h
Source file repositories/reference/linux-study-clean/arch/arm64/boot/dts/freescale/imx94-power.h
File Facts
- System
- Linux kernel
- Corpus path
arch/arm64/boot/dts/freescale/imx94-power.h- Extension
.h- Size
- 953 bytes
- Lines
- 42
- 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 __IMX94_POWER_H
#define __IMX94_POWER_H
#define IMX94_PD_ANA 0
#define IMX94_PD_AON 1
#define IMX94_PD_BBSM 2
#define IMX94_PD_M71 3
#define IMX94_PD_CCMSRCGPC 4
#define IMX94_PD_A55C0 5
#define IMX94_PD_A55C1 6
#define IMX94_PD_A55C2 7
#define IMX94_PD_A55C3 8
#define IMX94_PD_A55P 9
#define IMX94_PD_DDR 10
#define IMX94_PD_DISPLAY 11
#define IMX94_PD_M70 12
#define IMX94_PD_HSIO_TOP 13
#define IMX94_PD_HSIO_WAON 14
#define IMX94_PD_NETC 15
#define IMX94_PD_NOC 16
#define IMX94_PD_NPU 17
#define IMX94_PD_WAKEUP 18
#define IMX94_PERF_M33 0
#define IMX94_PERF_M33S 1
#define IMX94_PERF_WAKEUP 2
#define IMX94_PERF_M70 3
#define IMX94_PERF_M71 4
#define IMX94_PERF_DRAM 5
#define IMX94_PERF_HSIO 6
#define IMX94_PERF_NPU 7
#define IMX94_PERF_NOC 8
#define IMX94_PERF_A55 9
#define IMX94_PERF_DISP 10
#endif /* __IMX94_POWER_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.