> -----Original Message----- > From: Santosh Shilimkar [mailto:santosh.shilim...@ti.com] > Sent: Sunday, January 16, 2011 11:56 AM > To: Paul Walmsley; Russell King - ARM Linux > Cc: linux-omap@vger.kernel.org > Subject: RE: State of SDP4430 platform > > > -----Original Message----- > > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > > ow...@vger.kernel.org] On Behalf Of Paul Walmsley > > Sent: Sunday, January 16, 2011 11:37 AM > > To: Russell King - ARM Linux > > Cc: linux-omap@vger.kernel.org > > Subject: Re: State of SDP4430 platform > >
[.....] > > > Other stuff that shows in this boot log: > > > > ... > > > > > - Bunch of regulators are returning errors (is this a problem?) > > > - I2C timeouts which add quite a bit to the boot-time > > > > These two are probably related. Looks like something is wrong > with > > communication with the TWL/TPS PMIC on that board. Those problems > > don't > > show up on the OMAP4430ES2 Panda here, so they are probably > > 4430SDP-specific. > > > > > Actually I don't see these errors which ring a bell. There was an > I2C pull related issue with ES1.0 silicon. I guess these timeouts > would show up only on ES1.0 OMAP4 boards and not on ES2.0 boards. > > Monday I will check on my ES1.0 board and if needed send an updated > bootloader ( setting up right pull values) or a patch to kernel. > The I2C timeout issue I could reproduce on my ES1.0 board. It's ES1.0 specific issue because I2C burst mode wasn't fuctional on it. Twl RTC driver uses I2C burst mode and hence it times out. Other TWL I2C module has no such issue. The pull work-around we tried was not reliable hence it was dropped. In short the TWL RTC driver won't function on ES1.0. Apart from that rest of the I2C clients should work as usual. Regards, Santosh -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
