Luke Gong <lukejg...@gmail.com> writes: > Thanks, Kevin. > > On Thu, Jan 20, 2011 at 5:54 PM, Kevin Hilman <khil...@ti.com> wrote: >> Luke Gong <lukejg...@gmail.com> writes: >> >>> I have a beagle board with OMAP3530. I ported linux-omap-pm2.6.32 to >>> this board. When I want to let it suspend to ram, >> >> This is an old kernel. Any reason you're not using a newer kernel? > > I have Angstrom7 with kernel 2.6.32 running on this board. So I > selected this old version to test. I might try the latest one. >
You'll have to get support from the folks making the Angstrom kernel as I don't keep track of the kernel baseline they use or the local patches they apply, so can't help you. If you can reproduce on current linux-omap, I'll be glad to help. Kevin >> >>> it fails and I get >>> the message "Class driver suspend failed for cpu0" >> >> This is the CPUfreq driver failing to suspend, probably because there is >> no CPUfreq driver implemented in your kernel. Try disabling CPU_FREQ in >> your kernel config. > > It seems can suspend to ram after disabling CPU_FREQ. Here is the log: > > root@beagleboard:~# echo mem > /sys/power/state > PM: Syncing filesystems ... done. > Freezing user space processes ... (elapsed 0.00 seconds) done. > Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. > Suspending console(s) (use no_console_suspend to debug) > > ************************************************************* > Once I hit the keyboard, I get: > > root@beagleboard:~# echo mem > /sys/power/state > PM: Syncing filesystems ... done. > Freezing user space processes ... (elapsed 0.00 seconds) done. > Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. > Suspending console(s) (use no_console_suspend to debug) > omapfb omapfb: timeout waiting for FRAME DONE > Powerdomain (core_pwrdm) didn't enter target state 1 > Powerdomain (cam_pwrdm) didn't enter target state 1 > Powerdomain (per_pwrdm) didn't enter target state 1 > Could not enter target state in pm_suspend > Restarting tasks ... done. > root@beagleboard:~# > *************************************************** > > I am just curious why the powerdomain didn't enter target state 1. > > Another issue is about CPU frequency scaling. Using the original > Angstrom7, I can scale CPU frequency. But with the linux-omap-pm > kernel, I cannot do it even though I enable this feature in the config > file. Is there any solution to support both cpu frequency scaling and > suspend to ram? > > Thanks again for your help. >> >> Kevin >> >>> . Here is the log: >>> >>> root@beagleboard:~# echo mem > /sys/power/state >>> PM: Syncing filesystems ... done. >>> Freezing user space processes ... (elapsed 0.00 seconds) done. >>> Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. >>> Suspending console(s) (use no_console_suspend to debug) >>> omapfb omapfb: timeout waiting for FRAME DONE >>> Class driver suspend failed for cpu0 >>> Restarting tasks ... done. >>> >>> ********************************************* >>> >>> Is there any idea to fix this problem? Thanks. >> -- 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
