drivers/media/dvb-frontends/or51132.h
Source file repositories/reference/linux-study-clean/drivers/media/dvb-frontends/or51132.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/dvb-frontends/or51132.h- Extension
.h- Size
- 882 bytes
- Lines
- 36
- 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/firmware.hlinux/dvb/frontend.h
Detected Declarations
struct or51132_configfunction or51132_attach
Annotated Snippet
#ifndef OR51132_H
#define OR51132_H
#include <linux/firmware.h>
#include <linux/dvb/frontend.h>
struct or51132_config
{
/* The demodulator's i2c address */
u8 demod_address;
/* Need to set device param for start_dma */
int (*set_ts_params)(struct dvb_frontend* fe, int is_punctured);
};
#if IS_REACHABLE(CONFIG_DVB_OR51132)
extern struct dvb_frontend* or51132_attach(const struct or51132_config* config,
struct i2c_adapter* i2c);
#else
static inline struct dvb_frontend* or51132_attach(const struct or51132_config* config,
struct i2c_adapter* i2c)
{
printk(KERN_WARNING "%s: driver disabled by Kconfig\n", __func__);
return NULL;
}
#endif // CONFIG_DVB_OR51132
#endif // OR51132_H
Annotation
- Immediate include surface: `linux/firmware.h`, `linux/dvb/frontend.h`.
- Detected declarations: `struct or51132_config`, `function or51132_attach`.
- 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.