drivers/video/fbdev/arkfb.c

File Facts

System

Linux kernel

Corpus path

drivers/video/fbdev/arkfb.c

Extension

.c

Size

32817 bytes

Lines

1219

Domain

Driver Families

Bucket

drivers/video

Inferred role

Driver Families: operation-table or driver-model contract

Status

pattern 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.
• Defines an operation table; this is where Linux turns generic core objects into subsystem-specific behavior.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• 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/aperture.h
• linux/module.h
• linux/kernel.h
• linux/errno.h
• linux/string.h
• linux/mm.h
• linux/tty.h
• linux/slab.h
• linux/delay.h
• linux/fb.h
• linux/svga.h
• linux/init.h
• linux/pci.h
• linux/console.h
• video/vga.h

Detected Declarations

• struct arkfb_info
• struct dac_ops
• struct dac_info
• struct ics5342_info
• function arkfb_settile
• function arkfb_tilecursor
• function expand_color
• function arkfb_iplan_imageblit
• function arkfb_iplan_fillrect
• function expand_pixel
• function arkfb_cfb4_imageblit
• function arkfb_imageblit
• function arkfb_fillrect
• function dac_read_regs
• function dac_write_reg
• function dac_write_regs
• function dac_set_mode
• function dac_set_freq
• function dac_release
• function ics5342_set_mode
• function ics5342_set_freq
• function ics5342_release
• function ics5342_init
• function ark_dac_read_regs
• function ark_dac_write_regs
• function ark_set_pixclock
• function arkfb_open
• function arkfb_release
• function arkfb_check_var
• function arkfb_set_par
• function arkfb_setcolreg
• function arkfb_blank
• function arkfb_pan_display
• function ark_pci_probe
• function ark_pci_remove
• function ark_pci_suspend
• function ark_pci_resume
• function arkfb_cleanup
• function arkfb_init
• module init arkfb_init

Annotated Snippet

static struct pci_driver arkfb_pci_driver = {
	.name		= "arkfb",
	.id_table	= ark_devices,
	.probe		= ark_pci_probe,
	.remove		= ark_pci_remove,
	.driver.pm	= &ark_pci_pm_ops,
};

/* Cleanup */

static void __exit arkfb_cleanup(void)
{
	pr_debug("arkfb: cleaning up\n");
	pci_unregister_driver(&arkfb_pci_driver);
}

/* Driver Initialisation */

static int __init arkfb_init(void)
{

#ifndef MODULE
	char *option = NULL;
#endif

	if (fb_modesetting_disabled("arkfb"))
		return -ENODEV;

#ifndef MODULE
	if (fb_get_options("arkfb", &option))
		return -ENODEV;

	if (option && *option)
		mode_option = option;
#endif

	pr_debug("arkfb: initializing\n");
	return pci_register_driver(&arkfb_pci_driver);
}

module_init(arkfb_init);
module_exit(arkfb_cleanup);

Annotation

• Immediate include surface: `linux/aperture.h`, `linux/module.h`, `linux/kernel.h`, `linux/errno.h`, `linux/string.h`, `linux/mm.h`, `linux/tty.h`, `linux/slab.h`.
• Detected declarations: `struct arkfb_info`, `struct dac_ops`, `struct dac_info`, `struct ics5342_info`, `function arkfb_settile`, `function arkfb_tilecursor`, `function expand_color`, `function arkfb_iplan_imageblit`, `function arkfb_iplan_fillrect`, `function expand_pixel`.
• Atlas domain: Driver Families / drivers/video.
• Implementation status: pattern implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.

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.