On 11/27/2013 04:22 PM, Enric Balletbo Serra wrote:
Hi Thomas,
2013/11/27 Thomas Petazzoni thomas.petazzoni@free-electrons.com:
Dear Enric Balletbo Serra,
On Wed, 27 Nov 2013 14:56:15 +0100, Enric Balletbo Serra wrote:
2013/11/27 Thomas Petazzoni thomas.petazzoni@free-electrons.com:
Hello,
We've recently updated from u-boot 2013.04 to u-boot 2013.10 on our IGEP boards (OMAP3 based, U-Boot shows "OMAP36XX/37XX-GP ES1.2"), and we're seeing random I2C communication problems at startup.
Right, I've reproduced the issue. Any OMAP3-based board affected for this issue ?
Not sure to understand your question: my paragraph above mentions the IGEP board as being the platform on which I'm seeing this. So indeed, a OMAP3-based board is affected. But maybe I misunderstood your question.
Oops, sorry, bad question :)
Anybody knows if other OMAP3-based boards are affected for this issue ?
Our boards were also affected by this, and I managed to track the problem down to the zeroing of cnt register at the end of write, which was not present in the original version of the driver and appears to be triggering an issue that is mentioned in OMAP3 errata.
I just posted a patch to address this problem. You can find it here: http://patchwork.ozlabs.org/patch/294593/