drivers/video/fbdev/mb862xx/mb862xxfbdrv.c

File Facts

System

Linux kernel

Corpus path

drivers/video/fbdev/mb862xx/mb862xxfbdrv.c

Extension

.c

Size

30566 bytes

Lines

1208

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.
• Touches user memory; correctness depends on fault-safe copying and privilege boundary handling.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/aperture.h
• linux/fb.h
• linux/delay.h
• linux/uaccess.h
• linux/module.h
• linux/init.h
• linux/interrupt.h
• linux/pci.h
• linux/of.h
• linux/of_address.h
• linux/of_irq.h
• linux/platform_device.h
• mb862xxfb.h
• mb862xx_reg.h

Detected Declarations

• function h_total
• function v_total
• function hsp
• function vsp
• function d_pitch
• function chan_to_field
• function mb862xxfb_setcolreg
• function mb862xxfb_check_var
• function mb862xxfb_set_par
• function mb862xxfb_pan
• function mb862xxfb_blank
• function mb862xxfb_ioctl
• function mb862xxfb_init_fbinfo
• function dispregs_show
• function mb862xx_intr
• function GDC
• function of_platform_mb862xx_probe
• function of_platform_mb862xx_remove
• function coralp_init
• function init_dram_ctrl
• function carmine_init
• function mb862xx_pci_gdc_init
• function mb862xx_pci_probe
• function mb862xx_pci_remove
• function mb862xxfb_init
• function mb862xxfb_exit
• module init mb862xxfb_init

Annotated Snippet

static struct pci_driver mb862xxfb_pci_driver = {
	.name		= DRV_NAME,
	.id_table	= mb862xx_pci_tbl,
	.probe		= mb862xx_pci_probe,
	.remove		= mb862xx_pci_remove,
};
#endif

static int mb862xxfb_init(void)
{
	int ret = -ENODEV;

	if (fb_modesetting_disabled(DRV_NAME))
		return -ENODEV;

#if defined(CONFIG_FB_MB862XX_LIME)
	ret = platform_driver_register(&of_platform_mb862xxfb_driver);
#endif
#if defined(CONFIG_FB_MB862XX_PCI_GDC)
	ret = pci_register_driver(&mb862xxfb_pci_driver);
#endif
	return ret;
}

static void __exit mb862xxfb_exit(void)
{
#if defined(CONFIG_FB_MB862XX_LIME)
	platform_driver_unregister(&of_platform_mb862xxfb_driver);
#endif
#if defined(CONFIG_FB_MB862XX_PCI_GDC)
	pci_unregister_driver(&mb862xxfb_pci_driver);
#endif
}

module_init(mb862xxfb_init);
module_exit(mb862xxfb_exit);

MODULE_DESCRIPTION("Fujitsu MB862xx Framebuffer driver");
MODULE_AUTHOR("Anatolij Gustschin <agust@denx.de>");
MODULE_LICENSE("GPL v2");

Annotation

• Immediate include surface: `linux/aperture.h`, `linux/fb.h`, `linux/delay.h`, `linux/uaccess.h`, `linux/module.h`, `linux/init.h`, `linux/interrupt.h`, `linux/pci.h`.
• Detected declarations: `function h_total`, `function v_total`, `function hsp`, `function vsp`, `function d_pitch`, `function chan_to_field`, `function mb862xxfb_setcolreg`, `function mb862xxfb_check_var`, `function mb862xxfb_set_par`, `function mb862xxfb_pan`.
• Atlas domain: Driver Families / drivers/video.
• Implementation status: pattern implementation candidate.
• This snippet crosses the user/kernel memory boundary; validate fault handling and access checks before translating the pattern.
• 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.