Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx> writes: > On Fri, 10 Sep 2010 14:54:23 -0700 > Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> wrote: > >> It's the CPUfreq driver that's failing to suspend. > > Ok. > >> Yes, CPUfreq is not supported in l-o master or pm-core (only in the >> full pm branch.) If you Kconfig out CPUfreq, this failure will go >> away. > > Aah, yes, I forgot about this. I know it's temporary, but wouldn't it > be good to disable CPUfreq in omap3_defconfig in this case ? Yes. > BTW, I'm now seeing: > > [ 37.830596] Powerdomain (core_pwrdm) didn't enter target state 1 > [ 37.830627] Powerdomain (dss_pwrdm) didn't enter target state 1 > > when the system is woken up. Looks like DSS has not been initialized, so is not hitting RET. Do you have the DSS driver enabled and built-in? Without this (and until we have DSS converted to hwmod) the DSS HW is not in a state that can hit the low power mode. If the DSS driver is allowed to initialize, even without a panel, it should set the DSS HW in a state that will then allow RET. 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
