drivers/media/test-drivers/vivid/vivid-core.c
Source file repositories/reference/linux-study-clean/drivers/media/test-drivers/vivid/vivid-core.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/test-drivers/vivid/vivid-core.c- Extension
.c- Size
- 75519 bytes
- Lines
- 2341
- 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.
- 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.hlinux/errno.hlinux/kernel.hlinux/init.hlinux/sched.hlinux/slab.hlinux/vmalloc.hlinux/font.hlinux/mutex.hlinux/platform_device.hlinux/videodev2.hlinux/v4l2-dv-timings.hmedia/videobuf2-vmalloc.hmedia/videobuf2-dma-contig.hmedia/v4l2-dv-timings.hmedia/v4l2-ioctl.hmedia/v4l2-fh.hmedia/v4l2-event.hvivid-core.hvivid-vid-common.hvivid-vid-cap.hvivid-vid-out.hvivid-radio-common.hvivid-radio-rx.hvivid-radio-tx.hvivid-sdr-cap.hvivid-vbi-cap.hvivid-vbi-out.hvivid-osd.hvivid-cec.hvivid-ctrls.hvivid-meta-cap.h
Detected Declarations
function vidioc_querycapfunction vidioc_s_hw_freq_seekfunction vidioc_enum_freq_bandsfunction vidioc_g_tunerfunction vidioc_s_tunerfunction vidioc_g_frequencyfunction vidioc_s_frequencyfunction vidioc_overlayfunction vidioc_g_fbuffunction vidioc_s_fbuffunction vidioc_s_stdfunction vidioc_s_dv_timingsfunction vidioc_g_pixelaspectfunction vidioc_g_selectionfunction vidioc_s_selectionfunction vidioc_g_parmfunction vidioc_s_parmfunction vidioc_log_statusfunction vivid_radio_readfunction vivid_radio_writefunction vivid_radio_pollfunction vivid_enum_inputfunction vivid_g_inputfunction vivid_s_inputfunction vivid_enum_fmt_capfunction vivid_g_fmt_capfunction vivid_try_fmt_capfunction vivid_s_fmt_capfunction vivid_g_fmt_cap_mplanefunction vivid_try_fmt_cap_mplanefunction vivid_s_fmt_cap_mplanefunction vivid_is_in_usefunction vivid_is_last_userfunction vivid_reconnectfunction vivid_fop_releasefunction vivid_is_last_userfunction vidioc_reqbufsfunction vidioc_create_bufsfunction vivid_dev_releasefunction vivid_req_validatefunction vivid_create_queuefunction vivid_detect_feature_setfunction vivid_set_capabilitiesfunction vivid_disable_unused_ioctlsfunction vivid_init_dv_timingsfunction vivid_create_queuesfunction vivid_create_devnodesfunction update_hdmi_ctrls_work_handler
Annotated Snippet
module_init(vivid_init);
module_exit(vivid_exit);
Annotation
- Immediate include surface: `linux/module.h`, `linux/errno.h`, `linux/kernel.h`, `linux/init.h`, `linux/sched.h`, `linux/slab.h`, `linux/vmalloc.h`, `linux/font.h`.
- Detected declarations: `function vidioc_querycap`, `function vidioc_s_hw_freq_seek`, `function vidioc_enum_freq_bands`, `function vidioc_g_tuner`, `function vidioc_s_tuner`, `function vidioc_g_frequency`, `function vidioc_s_frequency`, `function vidioc_overlay`, `function vidioc_g_fbuf`, `function vidioc_s_fbuf`.
- 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.
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.