drivers/video/fbdev/omap/omapfb_main.c

File Facts

System

Linux kernel

Corpus path

drivers/video/fbdev/omap/omapfb_main.c

Extension

.c

Size

46943 bytes

Lines

1926

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.
• 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/export.h
• linux/platform_device.h
• linux/mm.h
• linux/slab.h
• linux/uaccess.h
• linux/module.h
• linux/sysfs.h
• linux/omap-dma.h
• linux/soc/ti/omap1-soc.h
• omapfb.h
• lcdc.h

Detected Declarations

• struct caps_table_struct
• function omapdss_release
• function omapfb_rqueue_lock
• function omapfb_rqueue_unlock
• function ctrl_init
• function ctrl_cleanup
• function ctrl_change_mode
• function omapfb_open
• function omapfb_release
• function _setcolreg
• function omapfb_setcolreg
• function omapfb_setcmap
• function omapfb_blank
• function omapfb_sync
• function set_fb_fix
• function set_color_mode
• function set_fb_var
• function omapfb_pan_display
• function omapfb_mirror
• function omapfb_check_var
• function omapfb_set_par
• function omapfb_update_window_async
• function omapfb_update_win
• function omapfb_update_full_screen
• function omapfb_setup_plane
• function omapfb_query_plane
• function omapfb_setup_mem
• function omapfb_query_mem
• function omapfb_set_color_key
• function omapfb_get_color_key
• function omapfb_init_notifier
• function omapfb_register_client
• function omapfb_unregister_client
• function omapfb_notify_clients
• function omapfb_set_update_mode
• function omapfb_get_update_mode
• function omapfb_get_caps
• function omapfb_write_first_pixel
• function omapfb_ioctl
• function omapfb_mmap
• function omapfb_show_caps_num
• function omapfb_show_caps_text
• function omapfb_show_panel_name
• function omapfb_show_bklight_level
• function omapfb_store_bklight_level
• function omapfb_show_bklight_max
• function omapfb_show_ctrl_name
• function omapfb_register_sysfs

Annotated Snippet

module_init(omapfb_init);
module_exit(omapfb_cleanup);

MODULE_DESCRIPTION("TI OMAP framebuffer driver");
MODULE_AUTHOR("Imre Deak <imre.deak@nokia.com>");
MODULE_LICENSE("GPL");

Annotation

• Immediate include surface: `linux/export.h`, `linux/platform_device.h`, `linux/mm.h`, `linux/slab.h`, `linux/uaccess.h`, `linux/module.h`, `linux/sysfs.h`, `linux/omap-dma.h`.
• Detected declarations: `struct caps_table_struct`, `function omapdss_release`, `function omapfb_rqueue_lock`, `function omapfb_rqueue_unlock`, `function ctrl_init`, `function ctrl_cleanup`, `function ctrl_change_mode`, `function omapfb_open`, `function omapfb_release`, `function _setcolreg`.
• 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.

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.