drivers/video/fbdev/chipsfb.c

File Facts

System

Linux kernel

Corpus path

drivers/video/fbdev/chipsfb.c

Extension

.c

Size

12760 bytes

Lines

531

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/backlight.h
• 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/fb.h
• linux/pm.h
• linux/init.h
• linux/pci.h
• linux/console.h
• asm/backlight.h

Detected Declarations

• struct chips_init_reg
• function chipsfb_check_var
• function chipsfb_set_par
• function chipsfb_blank
• function chipsfb_setcolreg
• function chips_hw_init
• function init_chips
• function chipsfb_pci_init
• function chipsfb_remove
• function chipsfb_pci_suspend
• function chipsfb_pci_resume
• function chips_init
• function chipsfb_exit
• module init chips_init

Annotated Snippet

static struct pci_driver chipsfb_driver = {
	.name =		"chipsfb",
	.id_table =	chipsfb_pci_tbl,
	.probe =	chipsfb_pci_init,
	.remove =	chipsfb_remove,
#ifdef CONFIG_PM
	.suspend =	chipsfb_pci_suspend,
	.resume =	chipsfb_pci_resume,
#endif
};

int __init chips_init(void)
{
	if (fb_modesetting_disabled("chipsfb"))
		return -ENODEV;

	if (fb_get_options("chipsfb", NULL))
		return -ENODEV;

	return pci_register_driver(&chipsfb_driver);
}

module_init(chips_init);

static void __exit chipsfb_exit(void)
{
	pci_unregister_driver(&chipsfb_driver);
}

MODULE_DESCRIPTION("Chips & Technologies 65550 frame buffer driver");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/aperture.h`, `linux/backlight.h`, `linux/module.h`, `linux/kernel.h`, `linux/errno.h`, `linux/string.h`, `linux/mm.h`, `linux/vmalloc.h`.
• Detected declarations: `struct chips_init_reg`, `function chipsfb_check_var`, `function chipsfb_set_par`, `function chipsfb_blank`, `function chipsfb_setcolreg`, `function chips_hw_init`, `function init_chips`, `function chipsfb_pci_init`, `function chipsfb_remove`, `function chipsfb_pci_suspend`.
• 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.