> I've experienced problem with OMAP5910 I2C driver in my custom board. > It freezes after some working time. > When it freezes, register I2C_STAT show that XUDF (or ROVR) bit is set > and SCL pin > is in low state. > I2C_CNT register is not zero too, but buf_len counter is zero. > Attempt to use init() function do not help in this situation. > Only things I can do with it - set I2C to debug mode and make some SCL > clocks by hand. > After this I2C state machine can work for some time. > When I2C clock is set to 100kHz it happens almost in every transfer - I > try to read/write > EEPROM. In 20kHz it still can happen too (on heavy load much frequently). > It's look like internal I2C state machine is broken. > So, for now I replace i2c algorithm with i2c_algo_bit and everything > works fine. > > I'm curious - only I have such a problem with I2C bus in OMAP 5910 or > someone else too? > May be there is better solution? I cannot say specifically, but I would recommend that you check out the OMAP5910 device errata document and see if any of the known silicon defects regarding the i2c peripheral could be impacting you. You can find the device errata here: http://focus.ti.com/docs/prod/folders/print/omap5910.html Cheers Jon -- 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
