Hi Kevin,
After following your instructions, setting
CONFIG_OMAP_RESET_CLOCKS, and applying all the 204 omap-pm patches, I
don't get any more error messages on the console. So this is a very
big improvement since I started incorporating the omap-pm patches for
my android-2.6.29 port to the overo platform.
Now there is only one issue left, which is you need to press the
touchscreen for a long time (around 3 secs) for it to get the system
to resume. There are no error messages now, but because it take a long
time to wake up from suspend mode, it gives the impression that the
system is un-responsive or stuck in suspend mode. Sometimes it doesnt
come out of suspend mode at all.
Here is the output from the console window:
request_suspend_state: wakeup (3->0) at 15586914111 (2000-01-01
00:00:14.131500245 UTC)
request_suspend_state: sleep (0->3) at 90151855487 (2000-01-01
00:01:28.696441621 UTC)
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)
n 0 loops
wakeup wake lock: mmc_delayed_work
mmc1: mmc_rescan - card ocr from io_op=0x00000000, err = -110
PM: resume devices took 0.554 seconds
Restarting tasks ... <7>hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
# done.
suspend: exit suspend, ret = 0 (2000-01-01 00:01:34.529602052 UTC)
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)
mmc1: mmc_rescan - card ocr from io_op=0x00000000, err = -110
PM: resume devices took 0.820 seconds
Restarting tasks ... <7>hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
request_suspend_state: wakeup (3->0) at 92972961452 (2000-01-01
00:01:51.524871827 UTC)
done.
suspend: exit suspend, ret = 0 (2000-01-01 00:01:51.550201418 UTC)
Best regards,
Elvis
--
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
