Age | Commit message (Collapse) | Author |
|
SAA7146 does not generate an I2C error irq when we are probing
for a non-existant device (so there's neither an ACK nor a NACK
at the end of the address phase)
- don't request the I2C error irq anymore, since it isn't currently
being handled; we just wait for the /BUSY irq or timeout; if there
were errors during transmission they will still be detected
from the status register after the /BUSY irq
- added some more debug to hw_interrupt()
TODO: I think SAA7146_I2C_TIMEOUT is too large; 10ms should do?
|
|
driver. I doesn't do any harm for my analog drivers and apparently fixes some
bugs related to some frontends/tuners, who expect certain start/stop cycles.
Please check if these tuners work now...
|
|
instead of busy waiting for an i2c transaction to finish. Left the
old method in there. if you need it (or if i screwed up),
set "use_i2c_irq" to zero in saa7146_i2c.c to get the old behaviour.
|
|
changed mxb to (un)register the i2c adapter by itself
|
|
READMEs accordingly, compile fixes for the mxb driver.
|
|
for the new saa7146 core, the mxb driver and the saa7111 driver.
|
|
|