drivers/video/fbdev/hpfb.c

File Facts

System

Linux kernel

Corpus path

drivers/video/fbdev/hpfb.c

Extension

.c

Size

11427 bytes

Lines

429

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.h
• linux/kernel.h
• linux/errno.h
• linux/string.h
• linux/mm.h
• linux/delay.h
• linux/init.h
• linux/fb.h
• linux/dio.h
• asm/io.h
• linux/uaccess.h

Detected Declarations

• function hpfb_setcolreg
• function hpfb_blank
• function topcat_blit
• function hpfb_copyarea
• function hpfb_fillrect
• function hpfb_sync
• function hpfb_init_one
• function hpfb_dio_probe
• function hpfb_remove_one
• function hpfb_init
• function hpfb_cleanup_module
• module init hpfb_init

Annotated Snippet

module_init(hpfb_init);
module_exit(hpfb_cleanup_module);

MODULE_LICENSE("GPL");

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 hpfb_setcolreg`, `function hpfb_blank`, `function topcat_blit`, `function hpfb_copyarea`, `function hpfb_fillrect`, `function hpfb_sync`, `function hpfb_init_one`, `function hpfb_dio_probe`, `function hpfb_remove_one`, `function hpfb_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.