drivers/media/test-drivers/vim2m.c

File Facts

System

Linux kernel

Corpus path

drivers/media/test-drivers/vim2m.c

Extension

.c

Size

39257 bytes

Lines

1616

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
• media/v4l2-common.h

Detected Declarations

• struct vim2m_fmt
• struct vim2m_q_data
• struct vim2m_dev
• struct vim2m_ctx
• function vim2m_dev_release
• function get_alignment
• function copy_line
• function copy_two_pixels
• function device_process
• function job_ready
• function job_abort
• function device_run
• function device_work
• function vidioc_querycap
• function enum_fmt
• function vidioc_enum_fmt_vid_cap
• function vidioc_enum_fmt_vid_out
• function vidioc_enum_framesizes
• function vidioc_g_fmt
• function vidioc_g_fmt_mplane
• function vidioc_g_fmt_vid_out
• function vidioc_g_fmt_vid_cap
• function vidioc_g_fmt_vid_out_mplane
• function vidioc_g_fmt_vid_cap_mplane
• function vidioc_try_fmt
• function vidioc_try_fmt_vid_cap
• function vidioc_try_fmt_vid_cap_mplane
• function vidioc_try_fmt_vid_out
• function vidioc_try_fmt_vid_out_mplane
• function vidioc_s_fmt
• function vidioc_s_fmt_vid_cap
• function vidioc_s_fmt_vid_cap_mplane
• function vidioc_s_fmt_vid_out
• function vidioc_s_fmt_vid_out_mplane
• function vim2m_s_ctrl
• function vim2m_queue_setup
• function vim2m_buf_out_validate
• function vim2m_buf_prepare
• function vim2m_buf_queue
• function vim2m_start_streaming
• function vim2m_stop_streaming
• function vim2m_buf_request_complete
• function queue_init
• function vim2m_open
• function vim2m_release
• function vim2m_device_release
• function vim2m_probe
• function vim2m_remove

Annotated Snippet

module_init(vim2m_init);
module_exit(vim2m_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 vim2m_fmt`, `struct vim2m_q_data`, `struct vim2m_dev`, `struct vim2m_ctx`, `function vim2m_dev_release`, `function get_alignment`, `function copy_line`, `function copy_two_pixels`, `function device_process`, `function job_ready`.
• 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.