drivers/media/usb/em28xx/em28xx-video.c

File Facts

System

Linux kernel

Corpus path

drivers/media/usb/em28xx/em28xx-video.c

Extension

.c

Size

83571 bytes

Lines

3106

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

• em28xx.h
• linux/init.h
• linux/list.h
• linux/module.h
• linux/kernel.h
• linux/bitmap.h
• linux/usb.h
• linux/i2c.h
• linux/mm.h
• linux/mutex.h
• linux/slab.h
• em28xx-v4l.h
• media/v4l2-common.h
• media/v4l2-ioctl.h
• media/v4l2-event.h
• media/drv-intf/msp3400.h
• media/tuner.h

Detected Declarations

• function norm_maxw
• function norm_maxh
• function em28xx_vbi_supported
• function em28xx_analogtv_supported
• function em28xx_wake_i2c
• function em28xx_colorlevels_set_default
• function em28xx_set_outfmt
• function em28xx_accumulator_set
• function em28xx_capture_area_set
• function em28xx_scaler_set
• function em28xx_resolution_set
• function em2828X_decoder_set_std
• function em28xx_set_alternate
• function finish_buffer
• function em28xx_copy_video
• function em28xx_copy_vbi
• function print_err_status
• function finish_field_prepare_next
• function process_frame_data_em28xx
• function process_frame_data_em25xx
• function em28xx_urb_data_copy
• function get_resource
• function res_get
• function res_free
• function em28xx_v4l2_media_release
• function em28xx_enable_analog_tuner
• function em28xx_v4l2_create_entities
• function queue_setup
• function buffer_prepare
• function em28xx_start_analog_streaming
• function em28xx_stop_streaming
• function em28xx_stop_vbi_streaming
• function buffer_queue
• function em28xx_vb2_setup
• function video_mux
• function em28xx_ctrl_notify
• function em28xx_s_ctrl
• function size_to_scale
• function scale_to_size
• function vidioc_g_fmt_vid_cap
• function vidioc_try_fmt_vid_cap
• function em28xx_set_video_format
• function vidioc_s_fmt_vid_cap
• function vidioc_g_std
• function vidioc_querystd
• function vidioc_s_std
• function vidioc_g_parm
• function vidioc_s_parm

Annotated Snippet

module_init(em28xx_video_register);
module_exit(em28xx_video_unregister);

Annotation

• Immediate include surface: `em28xx.h`, `linux/init.h`, `linux/list.h`, `linux/module.h`, `linux/kernel.h`, `linux/bitmap.h`, `linux/usb.h`, `linux/i2c.h`.
• Detected declarations: `function norm_maxw`, `function norm_maxh`, `function em28xx_vbi_supported`, `function em28xx_analogtv_supported`, `function em28xx_wake_i2c`, `function em28xx_colorlevels_set_default`, `function em28xx_set_outfmt`, `function em28xx_accumulator_set`, `function em28xx_capture_area_set`, `function em28xx_scaler_set`.
• 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.