drivers/media/dvb-frontends/stv0367_defs.h
Source file repositories/reference/linux-study-clean/drivers/media/dvb-frontends/stv0367_defs.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/media/dvb-frontends/stv0367_defs.h- Extension
.h- Size
- 44037 bytes
- Lines
- 1292
- 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
stv0367_regs.h
Detected Declarations
struct st_register
Annotated Snippet
struct st_register {
u16 addr;
u8 value;
};
/* values for STV4100 XTAL=30M int clk=53.125M*/
static const struct st_register def0367ter[] = {
{R367TER_ID, 0x60},
{R367TER_I2CRPT, 0xa0},
/* {R367TER_I2CRPT, 0x22},*/
{R367TER_TOPCTRL, 0x00},/* for xc5000; was 0x02 */
{R367TER_IOCFG0, 0x40},
{R367TER_DAC0R, 0x00},
{R367TER_IOCFG1, 0x00},
{R367TER_DAC1R, 0x00},
{R367TER_IOCFG2, 0x62},
{R367TER_SDFR, 0x00},
{R367TER_STATUS, 0xf8},
{R367TER_AUX_CLK, 0x0a},
{R367TER_FREESYS1, 0x00},
{R367TER_FREESYS2, 0x00},
{R367TER_FREESYS3, 0x00},
{R367TER_GPIO_CFG, 0x55},
{R367TER_GPIO_CMD, 0x00},
{R367TER_AGC2MAX, 0xff},
{R367TER_AGC2MIN, 0x00},
{R367TER_AGC1MAX, 0xff},
{R367TER_AGC1MIN, 0x00},
{R367TER_AGCR, 0xbc},
{R367TER_AGC2TH, 0x00},
{R367TER_AGC12C, 0x00},
{R367TER_AGCCTRL1, 0x85},
{R367TER_AGCCTRL2, 0x1f},
{R367TER_AGC1VAL1, 0x00},
{R367TER_AGC1VAL2, 0x00},
{R367TER_AGC2VAL1, 0x6f},
{R367TER_AGC2VAL2, 0x05},
{R367TER_AGC2PGA, 0x00},
{R367TER_OVF_RATE1, 0x00},
{R367TER_OVF_RATE2, 0x00},
{R367TER_GAIN_SRC1, 0xaa},/* for xc5000; was 0x2b */
{R367TER_GAIN_SRC2, 0xd6},/* for xc5000; was 0x04 */
{R367TER_INC_DEROT1, 0x55},
{R367TER_INC_DEROT2, 0x55},
{R367TER_PPM_CPAMP_DIR, 0x2c},
{R367TER_PPM_CPAMP_INV, 0x00},
{R367TER_FREESTFE_1, 0x00},
{R367TER_FREESTFE_2, 0x1c},
{R367TER_DCOFFSET, 0x00},
{R367TER_EN_PROCESS, 0x05},
{R367TER_SDI_SMOOTHER, 0x80},
{R367TER_FE_LOOP_OPEN, 0x1c},
{R367TER_FREQOFF1, 0x00},
{R367TER_FREQOFF2, 0x00},
{R367TER_FREQOFF3, 0x00},
{R367TER_TIMOFF1, 0x00},
{R367TER_TIMOFF2, 0x00},
{R367TER_EPQ, 0x02},
{R367TER_EPQAUTO, 0x01},
{R367TER_SYR_UPDATE, 0xf5},
{R367TER_CHPFREE, 0x00},
{R367TER_PPM_STATE_MAC, 0x23},
{R367TER_INR_THRESHOLD, 0xff},
{R367TER_EPQ_TPS_ID_CELL, 0xf9},
{R367TER_EPQ_CFG, 0x00},
{R367TER_EPQ_STATUS, 0x01},
{R367TER_AUTORELOCK, 0x81},
{R367TER_BER_THR_VMSB, 0x00},
{R367TER_BER_THR_MSB, 0x00},
{R367TER_BER_THR_LSB, 0x00},
{R367TER_CCD, 0x83},
{R367TER_SPECTR_CFG, 0x00},
{R367TER_CHC_DUMMY, 0x18},
{R367TER_INC_CTL, 0x88},
{R367TER_INCTHRES_COR1, 0xb4},
{R367TER_INCTHRES_COR2, 0x96},
{R367TER_INCTHRES_DET1, 0x0e},
{R367TER_INCTHRES_DET2, 0x11},
{R367TER_IIR_CELLNB, 0x8d},
{R367TER_IIRCX_COEFF1_MSB, 0x00},
{R367TER_IIRCX_COEFF1_LSB, 0x00},
{R367TER_IIRCX_COEFF2_MSB, 0x09},
{R367TER_IIRCX_COEFF2_LSB, 0x18},
{R367TER_IIRCX_COEFF3_MSB, 0x14},
{R367TER_IIRCX_COEFF3_LSB, 0x9c},
{R367TER_IIRCX_COEFF4_MSB, 0x00},
{R367TER_IIRCX_COEFF4_LSB, 0x00},
{R367TER_IIRCX_COEFF5_MSB, 0x36},
{R367TER_IIRCX_COEFF5_LSB, 0x42},
{R367TER_FEPATH_CFG, 0x00},
Annotation
- Immediate include surface: `stv0367_regs.h`.
- Detected declarations: `struct st_register`.
- 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.