drivers/media/test-drivers/vicodec/vicodec-core.c

File Facts

System

Linux kernel

Corpus path

drivers/media/test-drivers/vicodec/vicodec-core.c

Extension

.c

Size

62589 bytes

Lines

2253

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/module.h
• linux/delay.h
• linux/fs.h
• linux/sched.h
• linux/slab.h
• linux/platform_device.h
• media/v4l2-mem2mem.h
• media/v4l2-device.h
• media/v4l2-ioctl.h
• media/v4l2-ctrls.h
• media/v4l2-event.h
• media/videobuf2-vmalloc.h
• codec-v4l2-fwht.h

Detected Declarations

• struct pixfmt_info
• struct vicodec_q_data
• struct vicodec_dev_instance
• struct vicodec_dev
• struct vicodec_ctx
• function vicodec_dev_release
• function copy_cap_to_ref
• function validate_by_version
• function validate_stateless_params_flags
• function update_state_from_header
• function device_process
• function get_next_header
• function device_run
• function v4l2_m2m_is_last_draining_src_buf
• function job_remove_src_buf
• function info_from_header
• function is_header_valid
• function update_capture_data_from_header
• function set_last_buffer
• function job_ready
• function vidioc_querycap
• function enum_fmt
• function vidioc_enum_fmt_vid_cap
• function vidioc_enum_fmt_vid_out
• function vidioc_g_fmt
• function vidioc_g_fmt_vid_out
• function vidioc_g_fmt_vid_cap
• function vidioc_try_fmt
• function vidioc_try_fmt_vid_cap
• function vidioc_try_fmt_vid_out
• function vidioc_s_fmt
• function vidioc_s_fmt_vid_cap
• function vidioc_s_fmt_vid_out
• function vidioc_g_selection
• function vidioc_s_selection
• function vicodec_encoder_cmd
• function vicodec_decoder_cmd
• function vicodec_enum_framesizes
• function vicodec_subscribe_event
• function vicodec_queue_setup
• function vicodec_buf_out_validate
• function vicodec_buf_prepare
• function vicodec_buf_queue
• function V4L2_TYPE_IS_CAPTURE
• function vicodec_return_bufs
• function total_frame_size
• function vicodec_start_streaming
• function vicodec_stop_streaming

Annotated Snippet

module_init(vicodec_init);
module_exit(vicodec_exit);

Annotation

• Immediate include surface: `linux/module.h`, `linux/delay.h`, `linux/fs.h`, `linux/sched.h`, `linux/slab.h`, `linux/platform_device.h`, `media/v4l2-mem2mem.h`, `media/v4l2-device.h`.
• Detected declarations: `struct pixfmt_info`, `struct vicodec_q_data`, `struct vicodec_dev_instance`, `struct vicodec_dev`, `struct vicodec_ctx`, `function vicodec_dev_release`, `function copy_cap_to_ref`, `function validate_by_version`, `function validate_stateless_params_flags`, `function update_state_from_header`.
• 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.