drivers/media/pci/ddbridge/ddbridge-dummy-fe.c
Source file repositories/reference/linux-study-clean/drivers/media/pci/ddbridge/ddbridge-dummy-fe.c
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/pci/ddbridge/ddbridge-dummy-fe.c- Extension
.c- Size
- 3503 bytes
- Lines
- 154
- 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.
- 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/init.hlinux/string.hlinux/slab.hmedia/dvb_frontend.hddbridge-dummy-fe.h
Detected Declarations
struct ddbridge_dummy_fe_statefunction ddbridge_dummy_fe_read_statusfunction ddbridge_dummy_fe_read_berfunction ddbridge_dummy_fe_read_signal_strengthfunction ddbridge_dummy_fe_read_snrfunction ddbridge_dummy_fe_read_ucblocksfunction ddbridge_dummy_fe_get_frontendfunction ddbridge_dummy_fe_set_frontendfunction ddbridge_dummy_fe_sleepfunction ddbridge_dummy_fe_initfunction ddbridge_dummy_fe_releaseexport ddbridge_dummy_fe_qam_attach
Annotated Snippet
struct ddbridge_dummy_fe_state {
struct dvb_frontend frontend;
};
static int ddbridge_dummy_fe_read_status(struct dvb_frontend *fe,
enum fe_status *status)
{
*status = FE_HAS_SIGNAL
| FE_HAS_CARRIER
| FE_HAS_VITERBI
| FE_HAS_SYNC
| FE_HAS_LOCK;
return 0;
}
static int ddbridge_dummy_fe_read_ber(struct dvb_frontend *fe, u32 *ber)
{
*ber = 0;
return 0;
}
static int ddbridge_dummy_fe_read_signal_strength(struct dvb_frontend *fe,
u16 *strength)
{
*strength = 0;
return 0;
}
static int ddbridge_dummy_fe_read_snr(struct dvb_frontend *fe, u16 *snr)
{
*snr = 0;
return 0;
}
static int ddbridge_dummy_fe_read_ucblocks(struct dvb_frontend *fe, u32 *ucblocks)
{
*ucblocks = 0;
return 0;
}
/*
* Should only be implemented if it actually reads something from the hardware.
* Also, it should check for the locks, in order to avoid report wrong data
* to userspace.
*/
static int ddbridge_dummy_fe_get_frontend(struct dvb_frontend *fe,
struct dtv_frontend_properties *p)
{
return 0;
}
static int ddbridge_dummy_fe_set_frontend(struct dvb_frontend *fe)
{
if (fe->ops.tuner_ops.set_params) {
fe->ops.tuner_ops.set_params(fe);
if (fe->ops.i2c_gate_ctrl)
fe->ops.i2c_gate_ctrl(fe, 0);
}
return 0;
}
static int ddbridge_dummy_fe_sleep(struct dvb_frontend *fe)
{
return 0;
}
static int ddbridge_dummy_fe_init(struct dvb_frontend *fe)
{
return 0;
}
static void ddbridge_dummy_fe_release(struct dvb_frontend *fe)
{
struct ddbridge_dummy_fe_state *state = fe->demodulator_priv;
kfree(state);
}
static const struct dvb_frontend_ops ddbridge_dummy_fe_qam_ops;
struct dvb_frontend *ddbridge_dummy_fe_qam_attach(void)
{
struct ddbridge_dummy_fe_state *state = NULL;
/* allocate memory for the internal state */
state = kzalloc_obj(struct ddbridge_dummy_fe_state);
if (!state)
return NULL;
Annotation
- Immediate include surface: `linux/module.h`, `linux/init.h`, `linux/string.h`, `linux/slab.h`, `media/dvb_frontend.h`, `ddbridge-dummy-fe.h`.
- Detected declarations: `struct ddbridge_dummy_fe_state`, `function ddbridge_dummy_fe_read_status`, `function ddbridge_dummy_fe_read_ber`, `function ddbridge_dummy_fe_read_signal_strength`, `function ddbridge_dummy_fe_read_snr`, `function ddbridge_dummy_fe_read_ucblocks`, `function ddbridge_dummy_fe_get_frontend`, `function ddbridge_dummy_fe_set_frontend`, `function ddbridge_dummy_fe_sleep`, `function ddbridge_dummy_fe_init`.
- Atlas domain: Driver Families / drivers/media.
- Implementation status: integration 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.