arch/arm/mach-omap1/devices.c
Source file repositories/reference/linux-study-clean/arch/arm/mach-omap1/devices.c
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/mach-omap1/devices.c- Extension
.c- Size
- 8448 bytes
- Lines
- 364
- 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/dma-mapping.hlinux/module.hlinux/kernel.hlinux/init.hlinux/platform_device.hlinux/spi/spi.hlinux/platform_data/omap-wd-timer.hlinux/soc/ti/omap1-io.hasm/mach/map.htc.hmux.hhardware.hcommon.hclock.hmmc.hsram.h
Detected Declarations
function omap_init_rtcfunction omap_init_rtcfunction omap_mmc_addfunction omap1_init_mmcfunction omap_init_uwirefunction omap_init_uwirefunction omap1_init_rngfunction omap1_init_devicesfunction omap_init_wdtmodule init omap_init_wdt
Annotated Snippet
subsys_initcall(omap_init_wdt);
#endifAnnotation
- Immediate include surface: `linux/dma-mapping.h`, `linux/module.h`, `linux/kernel.h`, `linux/init.h`, `linux/platform_device.h`, `linux/spi/spi.h`, `linux/platform_data/omap-wd-timer.h`, `linux/soc/ti/omap1-io.h`.
- Detected declarations: `function omap_init_rtc`, `function omap_init_rtc`, `function omap_mmc_add`, `function omap1_init_mmc`, `function omap_init_uwire`, `function omap_init_uwire`, `function omap1_init_rng`, `function omap1_init_devices`, `function omap_init_wdt`, `module init omap_init_wdt`.
- 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.