Hi,
thanks for the comment.
> You should implement i2c adapter to demod driver and not add such glue
> to that USB-bridge. I mean that "relayed" stuff, i2c communication to
> tuner via demod. I2C-mux may not work I think as there is no gate-style
> multiplexing so you probably need plain i2c adapter. There is few
> examples already on some demod drivers.
I am afraid that the glue is actually necessary.
host - USB -> gl861 - I2C(1) -> tc90522 (addr:X)
\- I2C(2) -> tua6034 (addr:Y)
To send an i2c read message to tua6034,
one has to issue two transactions:
1. write via I2C(1) to addr:X, [ reg:0xfe, val: Y ]
2. read via I2C(1) from addr:X, [ out_data0, out_data1, ....]
The problem is that the transaction 1 is (somehow) implemented with
the different USB request than the other i2c transactions on I2C(1).
(this is confirmed by a packet capture on Windows box).
Although tc90522 already creats the i2c adapter for I2C(2),
tc90522 cannot know/control the USB implementation of I2C(1),
only the bridge driver can do this.
regards,
Akihiro
