> -----Original Message----- > From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap- > ow...@vger.kernel.org] On Behalf Of Jean Pihet > Sent: Friday, October 29, 2010 2:11 AM > To: linux-omap@vger.kernel.org > Cc: Kevin Hilman > Subject: OMAP3 low power mode broken on l-o > > Hi, > > The low power mode on the latest l-o master branch is broken, so I > investigated a bit. Here are the results. This has been tested on > OMAP3EVM and Beagleboard. > > The problem is that the CORE does not reach the desired mode (RET, > OFF). It is caused by the I2C1 fclk that is left enabled at suspend > time. > Extra printks has been added in the clock enable and disable functions > for I2C and a stack dump has been added in the suspend path if the > clock is still enabled, cf. log below. > > In the devices suspend sequence the RTC gets suspended, which triggers > a read of the TWL RTC through the I2C bus, which in turn enables the > I2C1 fclk. That clock is only disabled on devices resume. > > I am guessing this is linked to the recent changes in the I2C for HWMOD > support. > What is the correct fix to have the I2C modules correctly shut off > before the suspend? > > Any thoughts? Looks like get_sync / put_sync miss-match has re-appeared again which leads to I2C clocks are not getting cut.
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
