Mauro Carvalho Chehab wrote:
>> + tm6000_read_write_usb (dev, 0xc0, 0x10, 0x7f1f, 0x0000, buf, 2);
> Most of the calls there are read (0xc0). I don't know any device that requires
> a read for it to work. I suspect that the above code is just probing to check
> what i2c devices are found at the board.
Btw, by looking at drivers/media/dvb/frontends/zl10353_priv.h, we have an idea
on what the above does:
The register 0x7f is:
CHIP_ID = 0x7F,
So, basically, the above code is reading the ID of the chip, likely to be sure
that it
is a Zarlink 10353.
Cheers,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
