drivers/video/fbdev/pmag-ba-fb.c

File Facts

System

Linux kernel

Corpus path

drivers/video/fbdev/pmag-ba-fb.c

Extension

.c

Size

6432 bytes

Lines

291

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/compiler.h
• linux/errno.h
• linux/fb.h
• linux/init.h
• linux/kernel.h
• linux/module.h
• linux/tc.h
• linux/types.h
• asm/io.h
• video/pmag-ba-fb.h

Detected Declarations

• struct pmagbafb_par
• function dac_write
• function dac_read
• function pmagbafb_setcolreg
• function pmagbafb_erase_cursor
• function pmagbafb_probe
• function pmagbafb_remove
• function pmagbafb_init
• function pmagbafb_exit
• module init pmagbafb_init

Annotated Snippet

module_init(pmagbafb_init);
module_exit(pmagbafb_exit);

MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/compiler.h`, `linux/errno.h`, `linux/fb.h`, `linux/init.h`, `linux/kernel.h`, `linux/module.h`, `linux/tc.h`, `linux/types.h`.
• Detected declarations: `struct pmagbafb_par`, `function dac_write`, `function dac_read`, `function pmagbafb_setcolreg`, `function pmagbafb_erase_cursor`, `function pmagbafb_probe`, `function pmagbafb_remove`, `function pmagbafb_init`, `function pmagbafb_exit`, `module init pmagbafb_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.