arch/arm/mach-omap2/fb.c
Source file repositories/reference/linux-study-clean/arch/arm/mach-omap2/fb.c
File Facts
- System
- Linux kernel
- Corpus path
arch/arm/mach-omap2/fb.c- Extension
.c- Size
- 2924 bytes
- Lines
- 103
- 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/module.hlinux/kernel.hlinux/mm.hlinux/init.hlinux/platform_device.hlinux/memblock.hlinux/io.hlinux/omapfb.hlinux/dma-mapping.hasm/mach/map.hsoc.hdisplay.h
Detected Declarations
function omap_init_vrfbfunction omap_init_vrfbfunction omap_init_fbfunction omap_init_fb
Annotated Snippet
int __init omap_init_vrfb(void) { return 0; }
#endif
#if IS_ENABLED(CONFIG_FB_OMAP2)
static u64 omap_fb_dma_mask = ~(u32)0;
static struct omapfb_platform_data omapfb_config;
static struct platform_device omap_fb_device = {
.name = "omapfb",
.id = -1,
.dev = {
.dma_mask = &omap_fb_dma_mask,
.coherent_dma_mask = DMA_BIT_MASK(32),
.platform_data = &omapfb_config,
},
.num_resources = 0,
};
int __init omap_init_fb(void)
{
return platform_device_register(&omap_fb_device);
}
#else
int __init omap_init_fb(void) { return 0; }
#endif
Annotation
- Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/mm.h`, `linux/init.h`, `linux/platform_device.h`, `linux/memblock.h`, `linux/io.h`, `linux/omapfb.h`.
- Detected declarations: `function omap_init_vrfb`, `function omap_init_vrfb`, `function omap_init_fb`, `function omap_init_fb`.
- 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.