arch/arm/mach-omap2/omap54xx.h

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-omap2/omap54xx.h

Extension

.h

Size

1361 bytes

Lines

43

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 __ASM_SOC_OMAP54XX_H
#define __ASM_SOC_OMAP54XX_H

/*
 * Please place only base defines here and put the rest in device
 * specific headers.
 */
#define L4_54XX_BASE			0x4a000000
#define L4_WK_54XX_BASE			0x4ae00000
#define L4_PER_54XX_BASE		0x48000000
#define L3_54XX_BASE			0x44000000
#define OMAP54XX_32KSYNCT_BASE		0x4ae04000
#define OMAP54XX_CM_CORE_AON_BASE	0x4a004000
#define OMAP54XX_CM_CORE_BASE		0x4a008000
#define OMAP54XX_PRM_BASE		0x4ae06000
#define OMAP54XX_PRCM_MPU_BASE		0x48243000
#define OMAP54XX_SCM_BASE		0x4a002000
#define OMAP54XX_CTRL_BASE		0x4a002800
#define OMAP54XX_SAR_RAM_BASE		0x4ae26000

/* DRA7 specific base addresses */
#define L3_MAIN_SN_DRA7XX_BASE		0x44000000
#define L4_PER1_DRA7XX_BASE		0x48000000
#define L4_CFG_MPU_DRA7XX_BASE		0x48210000
#define L4_PER2_DRA7XX_BASE		0x48400000
#define L4_PER3_DRA7XX_BASE		0x48800000
#define L4_CFG_DRA7XX_BASE		0x4A000000
#define L4_WKUP_DRA7XX_BASE		0x4ae00000
#define DRA7XX_CM_CORE_AON_BASE		0x4a005000
#define DRA7XX_CTRL_BASE		0x4a003400
#define DRA7XX_TAP_BASE			0x4ae0c000

#endif /* __ASM_SOC_OMAP555554XX_H */

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.