drivers/media/usb/dvb-usb/cinergyT2.h
Source file repositories/reference/linux-study-clean/drivers/media/usb/dvb-usb/cinergyT2.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/usb/dvb-usb/cinergyT2.h- Extension
.h- Size
- 2339 bytes
- Lines
- 82
- 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/usb/input.hdvb-usb.h
Detected Declarations
struct dvbt_get_status_msgstruct dvbt_set_parameters_msgenum cinergyt2_ep1_cmd
Annotated Snippet
struct dvbt_get_status_msg {
uint32_t freq;
uint8_t bandwidth;
uint16_t tps;
uint8_t flags;
__le16 gain;
uint8_t snr;
__le32 viterbi_error_rate;
uint32_t rs_error_rate;
__le32 uncorrected_block_count;
uint8_t lock_bits;
uint8_t prev_lock_bits;
} __attribute__((packed));
struct dvbt_set_parameters_msg {
uint8_t cmd;
__le32 freq;
uint8_t bandwidth;
__le16 tps;
uint8_t flags;
} __attribute__((packed));
extern struct dvb_frontend *cinergyt2_fe_attach(struct dvb_usb_device *d);
#endif /* _DVB_USB_CINERGYT2_H_ */
Annotation
- Immediate include surface: `linux/usb/input.h`, `dvb-usb.h`.
- Detected declarations: `struct dvbt_get_status_msg`, `struct dvbt_set_parameters_msg`, `enum cinergyt2_ep1_cmd`.
- 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.