drivers/media/dvb-frontends/rtl2830_priv.h
Source file repositories/reference/linux-study-clean/drivers/media/dvb-frontends/rtl2830_priv.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/dvb-frontends/rtl2830_priv.h- Extension
.h- Size
- 828 bytes
- Lines
- 40
- 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
media/dvb_frontend.hlinux/int_log.hrtl2830.hlinux/i2c-mux.hlinux/math64.hlinux/regmap.hlinux/bitops.h
Detected Declarations
struct rtl2830_devstruct rtl2830_reg_val_mask
Annotated Snippet
struct rtl2830_dev {
struct rtl2830_platform_data *pdata;
struct i2c_client *client;
struct regmap *regmap;
struct i2c_mux_core *muxc;
struct dvb_frontend fe;
bool sleeping;
unsigned long filters;
enum fe_status fe_status;
u64 post_bit_error_prev; /* for old DVBv3 read_ber() calculation */
u64 post_bit_error;
u64 post_bit_count;
};
struct rtl2830_reg_val_mask {
u16 reg;
u8 val;
u8 mask;
};
#endif /* RTL2830_PRIV_H */
Annotation
- Immediate include surface: `media/dvb_frontend.h`, `linux/int_log.h`, `rtl2830.h`, `linux/i2c-mux.h`, `linux/math64.h`, `linux/regmap.h`, `linux/bitops.h`.
- Detected declarations: `struct rtl2830_dev`, `struct rtl2830_reg_val_mask`.
- 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.