drivers/media/dvb-frontends/m88rs2000.h
Source file repositories/reference/linux-study-clean/drivers/media/dvb-frontends/m88rs2000.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/dvb-frontends/m88rs2000.h- Extension
.h- Size
- 962 bytes
- Lines
- 50
- 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/dvb/frontend.hmedia/dvb_frontend.h
Detected Declarations
struct m88rs2000_config
Annotated Snippet
struct m88rs2000_config {
/* Demodulator i2c address */
u8 demod_addr;
u8 *inittab;
/* minimum delay before retuning */
int min_delay_ms;
int (*set_ts_params)(struct dvb_frontend *, int);
};
enum {
CALL_IS_SET_FRONTEND = 0x0,
CALL_IS_READ,
};
#if IS_REACHABLE(CONFIG_DVB_M88RS2000)
extern struct dvb_frontend *m88rs2000_attach(
const struct m88rs2000_config *config, struct i2c_adapter *i2c);
#else
static inline struct dvb_frontend *m88rs2000_attach(
const struct m88rs2000_config *config, struct i2c_adapter *i2c)
{
printk(KERN_WARNING "%s: driver disabled by Kconfig\n", __func__);
return NULL;
}
#endif /* CONFIG_DVB_M88RS2000 */
#define RS2000_FE_CRYSTAL_KHZ 27000
enum {
DEMOD_WRITE = 0x1,
WRITE_DELAY = 0x10,
};
#endif /* M88RS2000_H */
Annotation
- Immediate include surface: `linux/dvb/frontend.h`, `media/dvb_frontend.h`.
- Detected declarations: `struct m88rs2000_config`.
- 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.