On Friday 03 October 2008, Nathan Monson wrote: > > http://marc.info/?l=linux-omap&m=122297833314280&w=2 > > > > commenting on the issue I noted when I posted this patch; > > showing how I work around that specific I2C error. It'd > > likely work for you too. > > Thanks for pointing this out. The retry patch earlier in the thread > fixes the problem. > > On 5 test boots I received the "i2c_omap i2c_omap.1: controller timed > out" message all 5 times, but it recovers and seems to work fine. That's good news. Now, I'll hope someone more in touch with the I2C hardware can take a look at drivers/i2c/busses/i2c-omap.c and suggest some way to stop getting this error ... nice that it's rather reproducible, if one were to debug it! As I noted in the message above, I see this error in other cases too. All of them "of course" should be made to handle such faults better. But virtually nothing in the I2C stack does sane fault handling, so we also need the i2c-omap code to stop misbehaving. - Dave -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
