> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > owner@xxxxxxxxxxxxxxx] On Behalf Of Paul Walmsley > A brief update for anyone following along on the list: > > Aaro sent me a test-case. It seems that the receive overruns only affect > PM kernels. They are caused by the MPU going to sleep while it waits for > an I2C interrupt. It turns out that the current driver causes receive > overruns also; it just hides them. The receive overruns are fairly > straightforward to deal with by setting an MPU wakeup latency constraint > during I2C operations. What kind of latency is being seen by i2c in kernel snapshot you are using? Do you have an idea of what is tolerable given an I2C frequency? Is this error showing up in 100k/400k/HS mode? Sometimes a constraint is the only way but it does have cost. Regards, Richard W. -- 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
