[linux-dvb] LG Innotek TDVS-H062F / TDVS-H061F

[Mac Michaels]

This metal box has 3 different i2c addresses inside it. I am 
trying to properly structure the driver for it.The 
FusionHDTV 5 card uses an TDVS-H062F. I have a hack that 
works, but I must clean it up. Yes, I have a version of the 
FusionHDTV 5 driver that works and has been tested with 
8-VSB signals. QAM should work, but is not tested. I will 
release a patch after I get the code cleaned up.

The LG Innotek TDVS-H062F NIM tuner is a more sensitive 
version of the TDVS-H061F. The main differences between 
them is power consumption and noise specifications. They 
both program the same way. These are designed for USA and 
South Korea in that they handle NTSC and 8-VSB ATSC. They 
also support cable with QAM-64 and QAM256. There are three 
different parts inside that use three different i2c 
addresses.

TUA6034 Tuner at i2c address 0xC2 (0x61)

NTSC IF Demodulator at i2c address 0x86 (0x43)

LGDT3303 VSB/QAM Demodulator at address 0x1C (0x0e)

TUA6034 is a 3 band tuner that is controlled by a 4 byte i2c 
message. There is a small wart in that an additional 
setting can be made by setting a constant pattern into byte 
3 to affect the meaning of byte 4. This was cleanly handled 
by testing the tuner type to see if it has this capability.

NTSC IF Demodulator needs some help. I did some bad things 
to make this work. I grabbed the i2c-adapter from the 
TUA6034 and used a different i2c message address to twiddle 
the bits of the NTSC IF Demodulator. It is a hack that 
works but... 

NTSC IF Demodulator gets programmed differently from the 
TUA6034 tuner. It is on a different i2c address. It uses 
pairs of bytes in an address, value combination to set the 
program. It must be in one state for digital TV and another 
state for analog TV. It does not change when channel 
frequencies are changed. Should I create a new device for 
the NTSC IF Demodulator?

LGDT3303 is a complex chip that has its own driver. The 
driver also supports  LGDT3302. The chips are pin 
compatible, but many of the i2c addresses and data vary. 
Basic operation is very similar. This works well as a 
single driver for both chips.

-- Mac