arch/arm/mach-omap2/l4_3xxx.h
Source file repositories/reference/linux-study-clean/arch/arm/mach-omap2/l4_3xxx.h
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/mach-omap2/l4_3xxx.h- Extension
.h- Size
- 977 bytes
- Lines
- 30
- Domain
- Architecture Layer
- Bucket
- arch/arm
- 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 __ARCH_ARM_PLAT_OMAP_INCLUDE_MACH_L4_3XXX_H
#define __ARCH_ARM_PLAT_OMAP_INCLUDE_MACH_L4_3XXX_H
/* L4 CORE */
#define OMAP3_L4_CORE_FW_I2C1_REGION 21
#define OMAP3_L4_CORE_FW_I2C1_TA_REGION 22
#define OMAP3_L4_CORE_FW_I2C2_REGION 23
#define OMAP3_L4_CORE_FW_I2C2_TA_REGION 24
#define OMAP3_L4_CORE_FW_I2C3_REGION 73
#define OMAP3_L4_CORE_FW_I2C3_TA_REGION 74
/* Display Sub system (DSS) */
#define OMAP3_L4_CORE_FW_DSS_PROT_GROUP 2
#define OMAP3_L4_CORE_FW_DSS_DSI_REGION 104
#define OMAP3ES1_L4_CORE_FW_DSS_CORE_REGION 3
#define OMAP3_L4_CORE_FW_DSS_CORE_REGION 4
#define OMAP3_L4_CORE_FW_DSS_DISPC_REGION 4
#define OMAP3_L4_CORE_FW_DSS_RFBI_REGION 5
#define OMAP3_L4_CORE_FW_DSS_VENC_REGION 6
#define OMAP3_L4_CORE_FW_DSS_TA_REGION 7
#endif
Annotation
- Atlas domain: Architecture Layer / arch/arm.
- 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.