drivers/video/fbdev/vt8623fb.c

File Facts

System

Linux kernel

Corpus path

drivers/video/fbdev/vt8623fb.c

Extension

.c

Size

27280 bytes

Lines

955

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.
• 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/delay.h
• linux/fb.h
• linux/svga.h
• linux/init.h
• linux/pci.h
• linux/console.h
• video/vga.h

Detected Declarations

• struct vt8623fb_info
• function vt8623fb_tilecursor
• function expand_color
• function vt8623fb_iplan_imageblit
• function vt8623fb_iplan_fillrect
• function expand_pixel
• function vt8623fb_cfb4_imageblit
• function vt8623fb_imageblit
• function vt8623fb_fillrect
• function vt8623_set_pixclock
• function vt8623fb_open
• function vt8623fb_release
• function vt8623fb_check_var
• function vt8623fb_set_par
• function vt8623fb_setcolreg
• function vt8623fb_blank
• function vt8623fb_pan_display
• function vt8623_pci_probe
• function vt8623_pci_remove
• function vt8623_pci_suspend
• function vt8623_pci_resume
• function vt8623fb_cleanup
• function vt8623fb_init
• module init vt8623fb_init

Annotated Snippet

static struct pci_driver vt8623fb_pci_driver = {
	.name		= "vt8623fb",
	.id_table	= vt8623_devices,
	.probe		= vt8623_pci_probe,
	.remove		= vt8623_pci_remove,
	.driver.pm	= &vt8623_pci_pm_ops,
};

/* Cleanup */

static void __exit vt8623fb_cleanup(void)
{
	pr_debug("vt8623fb: cleaning up\n");
	pci_unregister_driver(&vt8623fb_pci_driver);
}

/* Driver Initialisation */

static int __init vt8623fb_init(void)
{

#ifndef MODULE
	char *option = NULL;
#endif

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

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

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

	pr_debug("vt8623fb: initializing\n");
	return pci_register_driver(&vt8623fb_pci_driver);
}

/* ------------------------------------------------------------------------- */

/* Modularization */

module_init(vt8623fb_init);
module_exit(vt8623fb_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/delay.h`.
• Detected declarations: `struct vt8623fb_info`, `function vt8623fb_tilecursor`, `function expand_color`, `function vt8623fb_iplan_imageblit`, `function vt8623fb_iplan_fillrect`, `function expand_pixel`, `function vt8623fb_cfb4_imageblit`, `function vt8623fb_imageblit`, `function vt8623fb_fillrect`, `function vt8623_set_pixclock`.
• 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.