'i2c read failed' problem
werner at openmoko.org
Wed Apr 18 07:47:08 CEST 2007
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:
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
/ Werner Almesberger, Buenos Aires, Argentina werner at almesberger.net /
More information about the openmoko-uboot