drivers/media/test-drivers/vidtv/vidtv_bridge.h
Source file repositories/reference/linux-study-clean/drivers/media/test-drivers/vidtv/vidtv_bridge.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/test-drivers/vidtv/vidtv_bridge.h- Extension
.h- Size
- 2322 bytes
- Lines
- 73
- Domain
- Driver Families
- Bucket
- drivers/media
- Inferred role
- Driver Families: implementation source
- Status
- source 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.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/i2c.hlinux/platform_device.hlinux/types.hmedia/dmxdev.hmedia/dvb_demux.hmedia/dvb_frontend.hmedia/media-device.hvidtv_mux.h
Detected Declarations
struct vidtv_dvb
Annotated Snippet
struct vidtv_dvb {
struct platform_device *pdev;
struct dvb_frontend *fe[NUM_FE];
struct dvb_adapter adapter;
struct dvb_demux demux;
struct dmxdev dmx_dev;
struct dmx_frontend dmx_fe[NUM_FE];
struct i2c_adapter i2c_adapter;
struct i2c_client *i2c_client_demod[NUM_FE];
struct i2c_client *i2c_client_tuner[NUM_FE];
u32 nfeeds;
struct mutex feed_lock; /* Protects access to the start/stop stream logic/data. */
bool streaming;
struct vidtv_mux *mux;
#ifdef CONFIG_MEDIA_CONTROLLER_DVB
struct media_device mdev;
#endif /* CONFIG_MEDIA_CONTROLLER_DVB */
};
#endif // VIDTV_BRIDG_H
Annotation
- Immediate include surface: `linux/i2c.h`, `linux/platform_device.h`, `linux/types.h`, `media/dmxdev.h`, `media/dvb_demux.h`, `media/dvb_frontend.h`, `media/media-device.h`, `vidtv_mux.h`.
- Detected declarations: `struct vidtv_dvb`.
- Atlas domain: Driver Families / drivers/media.
- Implementation status: source implementation candidate.
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.