Hello
> Check the dvb_gpio setting in the board profile. On some of those
> boards you need to take put one of the GPO pins high to take the demod
> out of reset. The KWorld 315u and 330u are both like that.
Absolutely true. Using the same pin setting as KWorld 330U made the I2C communication work correctly and the device is found.
Now the trouble is that scanning channels doesn't work, blue LED doesn't light up and the device is not heated up.
I'm quite newbie in this field, is there a good way to know what registers to set exactly?
I see that the working "mcentral" code had the following setting:
#define EETI_DEFAULT_GPIO { \
.ts1_on = _BIT_VAL(EM28XX_GPIO0, 0, 0), \
.a_on = _BIT_VAL(EM28XX_GPIO1, 0, 0), \
.xc3028_sec = _BIT_VAL(EM28XX_GPIO2, 1, 0), \
/* reserved */ \
.t1_reset = _BIT_VAL(EM28XX_GPIO4, 0, 1), \
/* reserved */ \
.t1_on = _BIT_VAL(EM28XX_GPIO6, 0, 0), \
.t2_on = _BIT_VAL(EM28XX_GPIO7, 1, 0), \
\
.l1_on = _BIT_VAL(EM28XX_GOP2, 1, 0), \
.d1_reset = _BIT_VAL(EM28XX_GOP3, 0, 1), \
}
But the v4l-dvb uses:
static struct em28xx_reg_seq kworld_330u_digital[] = {
{EM28XX_R08_GPIO, 0x6e, ~EM_GPIO_4, 10},
{EM2880_R04_GPO, 0x08, 0xff, 10},
{ -1, -1, -1, -1},
};
Lauri
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
