Hi Kevin,
I managed to successfully incorporate all your PM patches to the
linux-omap-2.6 master branch, for the gumstix overo earth (TI OMAP
3503). I am currently using it with Tomi's DSS2 (not the full set, but
the dss2.patch that comes with the overo openembedded repository.
When the device goes to suspend mode, and I immediately touch the
touch screen, to wake it up, two things happen:
a. it wakes up and immediately goes back to suspend.
b. if I touch it once more, a bit longer this time, it wakes up.
However, in the console, I see the following error message:
request_suspend_state: wakeup (3->0) at 14677886951 (2000-01-01
00:01:16.457611018 UTC)
request_suspend_state: sleep (0->3) at 76534332261 (2000-01-01
00:02:18.314025810 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)
PM: suspend devices took 0.226 seconds
Powerdomain (mpu_pwrdm) didn't enter target state 1
Powerdomain (neon_pwrdm) didn't enter target state 1
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
Powerdomain (usbhost_pwrdm) didn't enter target state 1
Could not enter target state in pm_suspend
wakeup wake lock: mmc_delayed_work
mmc1: mmc_rescan - card ocr from io_op=0x00000000, err = -110
PM: resume devices took 0.531 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:02:24.561462403 UTC)
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.00 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
What do these error messages indicate ?
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
