'i2c read failed' problem

[Werner Almesberger]

Harald Welte wrote:
> i just hate it flooding the i2c bus with requests for which we have
> clearly better ways to signalize it to the CPU.

Tentative and incomplete patch is in SVN:
trunk/src/target/u-boot/patches/unbusy-i2c.patch

I haven't tried it with GTA01Bv4 yet, where it probably fails since
the GPIO is (correctly) configured as an interrupt, not as an I/O.

When testing, I noticed that, when USB is attached, we constantly get
FCHGOK and CHGERR until we switch to fast charge mode. So if we're on
a slow-charge interface or the host doesn't talk to us, we may still
poll I2C like crazy.

I wonder if we need these two anyway. Perhaps we could just mask
them ?

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina     werner at almesberger.net /
/_http://www.almesberger.net/____________________________________________/