Peter Barada <peter.barada@xxxxxxxxxxx> writes: [...] >> What I can say based on the register dump you shared is that there is no >> obvious driver issue going on where a clock was left on by a driver. >> >> More than likely what is going on is that the booloader is using a >> device (e.g. USB, MMC) but is leaving it in a state such that that IP >> block cannot idle, so the CORE powerdomain then does not fully idle. >> In older kernels like this one, the linux drivers did not fully reset >> the hardware so bootloaders could cause problems like this (the u-boot >> on beagle has had several problems like this.) > > How can I determine if an IP block is not idled? Any suggestion where > to add code into the suspend patch to do such a check? > Unfortunatly, there is no easy way for OMAP3-based platforms. There are unfortunately several things that can be (mis)configured such that an IP block will not properly idle. This is one of the reasons that omap_hwmod was introduced. It gives a uniform way for IP blocks to be enabled, idled and shutdown so they are in an a known state. >> As a first whack at things, I would focus on USB OTG and MMC, as I've >> seen problem with both on other platforms, like Beagle. You need to >> ensure that both the these modules are fully reset either by the >> bootloader when it's done using them, or by the kernel in the early boot >> process. Current kernels now do the latter. > > Hmm, where in the current kernel is this done, device driver probe > functions or common platform init code? > As part of the initializion of omap_hwmod for a given IP block, the module is reset. Kevin -- 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
