drivers/video/fbdev/maxinefb.c
Source file repositories/reference/linux-study-clean/drivers/video/fbdev/maxinefb.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/video/fbdev/maxinefb.c- Extension
.c- Size
- 4594 bytes
- Lines
- 175
- Domain
- Driver Families
- Bucket
- drivers/video
- Inferred role
- Driver Families: exported/initcall integration point
- Status
- integration implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- 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.hlinux/kernel.hlinux/errno.hlinux/string.hlinux/mm.hlinux/delay.hlinux/init.hlinux/fb.hvideo/maxinefb.hasm/bootinfo.h
Detected Declarations
function maxinefb_ims332_write_registerfunction maxinefb_ims332_read_registerfunction maxinefb_setcolregfunction maxinefb_initfunction maxinefb_exitmodule init maxinefb_init
Annotated Snippet
module_init(maxinefb_init);
module_exit(maxinefb_exit);Annotation
- Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/errno.h`, `linux/string.h`, `linux/mm.h`, `linux/delay.h`, `linux/init.h`, `linux/fb.h`.
- Detected declarations: `function maxinefb_ims332_write_register`, `function maxinefb_ims332_read_register`, `function maxinefb_setcolreg`, `function maxinefb_init`, `function maxinefb_exit`, `module init maxinefb_init`.
- Atlas domain: Driver Families / drivers/video.
- 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.