drivers/video/fbdev/arcfb.c

File Facts

System

Linux kernel

Corpus path

drivers/video/fbdev/arcfb.c

Extension

.c

Size

15762 bytes

Lines

617

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Allocates kernel memory; connect allocation flags and lifetime to context constraints.
• 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/vmalloc.h
• linux/delay.h
• linux/interrupt.h
• linux/io.h
• linux/fb.h
• linux/init.h
• linux/arcfb.h
• linux/platform_device.h
• linux/uaccess.h

Detected Declarations

• struct arcfb_par
• function ks108_writeb_ctl
• function ks108_writeb_mainctl
• function ks108_readb_ctl2
• function ks108_writeb_data
• function ks108_set_start_line
• function ks108_set_yaddr
• function ks108_set_xaddr
• function ks108_clear_lcd
• function arcfb_open
• function arcfb_release
• function arcfb_pan_display
• function arcfb_interrupt
• function arcfb_lcd_update_page
• function arcfb_lcd_update_vert
• function arcfb_lcd_update_horiz
• function arcfb_lcd_update
• function arcfb_ioctl
• function arcfb_damage_range
• function arcfb_damage_area
• function arcfb_probe
• function arcfb_remove
• function arcfb_init
• function arcfb_exit
• module init arcfb_init

Annotated Snippet

module_init(arcfb_init);
module_exit(arcfb_exit);

MODULE_DESCRIPTION("fbdev driver for Arc monochrome LCD board");
MODULE_AUTHOR("Jaya Kumar");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/module.h`, `linux/kernel.h`, `linux/errno.h`, `linux/string.h`, `linux/mm.h`, `linux/vmalloc.h`, `linux/delay.h`, `linux/interrupt.h`.
• Detected declarations: `struct arcfb_par`, `function ks108_writeb_ctl`, `function ks108_writeb_mainctl`, `function ks108_readb_ctl2`, `function ks108_writeb_data`, `function ks108_set_start_line`, `function ks108_set_yaddr`, `function ks108_set_xaddr`, `function ks108_clear_lcd`, `function arcfb_open`.
• Atlas domain: Driver Families / drivers/video.
• Implementation status: integration implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• IRQ or DMA behavior appears here, which is relevant to the selected PCIe/NVMe device path.

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.