On Tue, Nov 6, 2012 at 5:31 AM, Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> wrote: > Jean Pihet <jean.pihet@xxxxxxxxxxxxxx> writes: > > [...] > >> I ran some intensive stress tests on the I2C and ... unfortunately I >> could not trigger the problem. It looks like the issue is caused by >> some transient situation where the CORE and/or I2C is in a low power >> state. > > FYI... I just ran across what appears to be the same bug on 3430/n900 > during suspend/resume testing. With CPUidle enabled, this happens every > time. > > Reverting the I2C QoS patch makes it work again. I think we should defer the release of the constraints Does this help http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg79841.html -- 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
