drivers/media/test-drivers/vidtv/vidtv_bridge.c

File Facts

System

Linux kernel

Corpus path

drivers/media/test-drivers/vidtv/vidtv_bridge.c

Extension

.c

Size

15721 bytes

Lines

617

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/dev_printk.h
• linux/moduleparam.h
• linux/mutex.h
• linux/platform_device.h
• linux/time.h
• linux/types.h
• linux/workqueue.h
• media/dvbdev.h
• media/media-device.h
• vidtv_bridge.h
• vidtv_common.h
• vidtv_demod.h
• vidtv_mux.h
• vidtv_ts.h
• vidtv_tuner.h

Detected Declarations

• function vidtv_bridge_mux_buf_sz_for_mux_rate
• function vidtv_bridge_check_demod_lock
• function vidtv_bridge_on_new_pkts_avail
• function vidtv_start_streaming
• function vidtv_stop_streaming
• function vidtv_start_feed
• function vidtv_stop_feed
• function vidtv_master_xfer
• function vidtv_i2c_func
• function vidtv_bridge_i2c_register_adap
• function vidtv_bridge_register_adap
• function vidtv_bridge_dmx_init
• function vidtv_bridge_dmxdev_init
• function vidtv_bridge_probe_demod
• function vidtv_bridge_probe_tuner
• function vidtv_bridge_dvb_init
• function vidtv_bridge_probe
• function vidtv_bridge_remove
• function vidtv_bridge_dev_release
• function vidtv_bridge_exit
• function vidtv_bridge_init
• module init vidtv_bridge_init

Annotated Snippet

module_init(vidtv_bridge_init);
module_exit(vidtv_bridge_exit);

MODULE_DESCRIPTION("Virtual Digital TV Test Driver");
MODULE_AUTHOR("Daniel W. S. Almeida");
MODULE_LICENSE("GPL");
MODULE_ALIAS("vidtv");
MODULE_ALIAS("dvb_vidtv");

Annotation

• Immediate include surface: `linux/dev_printk.h`, `linux/moduleparam.h`, `linux/mutex.h`, `linux/platform_device.h`, `linux/time.h`, `linux/types.h`, `linux/workqueue.h`, `media/dvbdev.h`.
• Detected declarations: `function vidtv_bridge_mux_buf_sz_for_mux_rate`, `function vidtv_bridge_check_demod_lock`, `function vidtv_bridge_on_new_pkts_avail`, `function vidtv_start_streaming`, `function vidtv_stop_streaming`, `function vidtv_start_feed`, `function vidtv_stop_feed`, `function vidtv_master_xfer`, `function vidtv_i2c_func`, `function vidtv_bridge_i2c_register_adap`.
• 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.