arch/arm/mach-pxa/pxa300.c

File Facts

System

Linux kernel

Corpus path

arch/arm/mach-pxa/pxa300.c

Extension

.c

Size

2204 bytes

Lines

98

Domain

Architecture Layer

Bucket

arch/arm

Inferred role

Architecture Layer: exported/initcall integration point

Status

integration 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.
• Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/module.h
• linux/kernel.h
• linux/platform_device.h
• linux/io.h
• linux/soc/pxa/cpu.h
• pxa300.h
• generic.h
• devices.h

Detected Declarations

• function pxa300_init
• module init pxa300_init

Annotated Snippet

core_initcall(pxa300_init);

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/platform_device.h`, `linux/io.h`, `linux/soc/pxa/cpu.h`, `pxa300.h`, `generic.h`, `devices.h`.
• Detected declarations: `function pxa300_init`, `module init pxa300_init`.
• Atlas domain: Architecture Layer / arch/arm.
• Implementation status: integration 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.