On Mon, Oct 22, 2012 at 6:12 PM, Jean Pihet <jean.pihet@xxxxxxxxxxxxxx> wrote: > Hi, > > On Sat, Oct 20, 2012 at 8:14 AM, Paul Walmsley <paul@xxxxxxxxx> wrote: >> Hi Jean >> >> On Fri, 19 Oct 2012, Paul Walmsley wrote: >> >>> On Thu, 18 Oct 2012, Paul Walmsley wrote: >>> >>> > Here are some basic OMAP test results for Linux v3.7-rc1. >>> > Logs and other details at http://www.pwsan.com/omap/testlogs/test_v3.7-rc1/ >> >> ... >> >>> > Failing tests: needing investigation >>> > ------------------------------------ >>> > >>> > Boot tests: >>> >>> * 3530ES3 Beagle: I2C timeouts during userspace init >>> - May be related to the threaded IRQ conversion of the I2C driver >>> - Unknown cause >> >> This one turned out to be caused by: >> >> commit 3db11feffc1ad2ab9dea27789e6b5b3032827adc >> Author: Jean Pihet <jean.pihet@xxxxxxxxxxxxxx> >> Date: Thu Sep 20 18:08:03 2012 +0200 >> >> ARM: OMAP: convert I2C driver to PM QoS for MPU latency constraints >> >> >> Reverting this commit causes the problem to go away, but since the OMAP PM >> constraint code was removed as well, it's unlikely that a simple revert is >> the right thing to do. >> >> Jean could you please investigate and fix this? > I tried the latest l-o with omap2plus defconfig on my Beagleboard B5 > (ES2.1) and could not reproduce the problem. > I do not have the I2C error messages at boot, nor at user space start > up. I tried to read/write the TWL RTC, successfully. > > Another difference is the bootloader images. I have the following: > - Texas Instruments X-Loader 1.4.2 (Feb 3 2009 - 15:34:17) > - U-Boot 2009.01-dirty (Feb 19 2009 - 12:22:31) > Could you send your bootloader images? > > I noticed you have I2C error messages in U-Boot, could that be the > cause of the I2C lock-up? > > On the PM QoS side the commit 3db11fef moves the I2C code from the > OMAP PM no-op layer to the PM QoS for CPU and DMA latency, which > influences the cpuidle states. However CPU_IDLE is not set in > omap2plus_defconfig so there should not be any effect. > Do you have CPU_IDLE enabled? FYI the issue is not present with CPU_IDLE enabled. Regards, Jean > >> >> >> - Paul > > Regards, > Jean -- 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
