drivers/media/dvb-frontends/drx39xyj/drx39xxj.h
Source file repositories/reference/linux-study-clean/drivers/media/dvb-frontends/drx39xyj/drx39xxj.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/dvb-frontends/drx39xyj/drx39xxj.h- Extension
.h- Size
- 722 bytes
- Lines
- 32
- 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.hdrx_driver.h
Detected Declarations
struct drx39xxj_state
Annotated Snippet
struct drx39xxj_state {
struct i2c_adapter *i2c;
struct drx_demod_instance *demod;
struct dvb_frontend frontend;
unsigned int i2c_gate_open:1;
const struct firmware *fw;
};
#if IS_REACHABLE(CONFIG_DVB_DRX39XYJ)
struct dvb_frontend *drx39xxj_attach(struct i2c_adapter *i2c);
#else
static inline struct dvb_frontend *drx39xxj_attach(struct i2c_adapter *i2c) {
return NULL;
};
#endif
#endif /* DVB_DUMMY_FE_H */
Annotation
- Immediate include surface: `linux/dvb/frontend.h`, `media/dvb_frontend.h`, `drx_driver.h`.
- Detected declarations: `struct drx39xxj_state`.
- 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.