drivers/media/usb/uvc/uvc_driver.c

File Facts

System

Linux kernel

Corpus path

drivers/media/usb/uvc/uvc_driver.c

Extension

.c

Size

93531 bytes

Lines

3321

Domain

Driver Families

Bucket

drivers/media

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.
• Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
• Touches IRQ or DMA behavior; this matters for the representative real-device path.
• 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/atomic.h
• linux/bits.h
• linux/gpio/consumer.h
• linux/kernel.h
• linux/list.h
• linux/module.h
• linux/slab.h
• linux/usb.h
• linux/usb/quirks.h
• linux/usb/uvc.h
• linux/videodev2.h
• linux/vmalloc.h
• linux/wait.h
• linux/unaligned.h
• media/v4l2-common.h
• media/v4l2-ioctl.h
• uvcvideo.h

Detected Declarations

• function uvc_colorspace
• function uvc_xfer_func
• function uvc_ycbcr_enc
• function list_for_each_entry
• function list_for_each_entry_continue
• function list_for_each_entry
• function uvc_stream_delete
• function uvc_parse_frame
• function uvc_parse_format
• function uvc_parse_streaming
• function uvc_entity_set_name
• function uvc_parse_vendor_control
• function uvc_parse_standard_control
• function uvc_parse_control
• function uvc_gpio_event
• function uvc_gpio_get_cur
• function uvc_gpio_get_info
• function uvc_gpio_irq
• function uvc_gpio_parse
• function uvc_gpio_init_irq
• function uvc_gpio_deinit
• function uvc_scan_chain_entity
• function uvc_scan_chain_forward
• function uvc_scan_chain_backward
• function uvc_scan_chain
• function uvc_print_terms
• function list_for_each_entry
• function uvc_scan_fallback
• function uvc_scan_device
• function list_for_each_entry
• function disconnect
• function list_for_each_safe
• function list_for_each_safe
• function list_for_each_safe
• function uvc_release
• function uvc_unregister_video
• function list_for_each_entry
• function uvc_register_video_device
• function uvc_register_video
• function uvc_register_terms
• function list_for_each_entry
• function uvc_register_chains
• function list_for_each_entry
• function uvc_probe
• function uvc_disconnect
• function uvc_suspend
• function list_for_each_entry
• function __uvc_resume

Annotated Snippet

module_init(uvc_init);
module_exit(uvc_cleanup);

MODULE_AUTHOR(DRIVER_AUTHOR);
MODULE_DESCRIPTION(DRIVER_DESC);
MODULE_LICENSE("GPL");
MODULE_VERSION(DRIVER_VERSION);

Annotation

• Immediate include surface: `linux/atomic.h`, `linux/bits.h`, `linux/gpio/consumer.h`, `linux/kernel.h`, `linux/list.h`, `linux/module.h`, `linux/slab.h`, `linux/usb.h`.
• Detected declarations: `function uvc_colorspace`, `function uvc_xfer_func`, `function uvc_ycbcr_enc`, `function list_for_each_entry`, `function list_for_each_entry_continue`, `function list_for_each_entry`, `function uvc_stream_delete`, `function uvc_parse_frame`, `function uvc_parse_format`, `function uvc_parse_streaming`.
• Atlas domain: Driver Families / drivers/media.
• Implementation status: integration implementation candidate.
• Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
• 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.