Hi Vikram,
Here is a posting of my observations after apply the defconfig and the mmc off patch set 1. BTW, Do let me know if I should be using mmc off patch set 1 or patch set 2, since both of them appear to be identical except for three entries.
Observation 01
----------------------
I get the following kernel error message on bootup, could you recommend a fix for this?
mmc1: mmc_rescan - card ocr from io_op=0x00000000, err = -110
regulator: Unable to get requested regulator: vmmc_aux
regulator: Unable to get requested regulator: vmmc
SR1: VDD autocomp is not active
Observation 02
----------------------
After the system goes to suspend mode, if I press the a key that sends an event via the serial UART3 debug console, it wakes up briefly and then immediately goes back to sleep, and I see the following messages on the console.
The same thing happens if I press the touchscreen briefly. I am using an ads7846 touchscreen controller connected to a 4.3" LG-Philips LCD display, with the gumstix overo earth (TI OMAP 3503) and palo43 board.
Powerdomain (core_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
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:04:08.555633537 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)
Observation 03
----------------------
If I press the touchscreen for a long time (> 2 secs), it comes out of suspend mode with the following error messages
Powerdomain (core_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
Restarting tasks ... <7>hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
request_suspend_state: wakeup (3->0) at 109015166614 (2000-01-01 00:04:37.537445064 UTC)
done.
suspend: exit suspend, ret = 0 (2000-01-01 00:04:37.575256342 UTC)
D/SurfaceFlinger( 888): Screen about to return, flinger = 0x16f328
I guess the first step would be to find out which of the mmc off patch sets (1 or 2) I should be apply. And then to know the root cause of the intermittent LCD wake up from suspend when you touch it briefly, or when you send a key press from the serial debug console.
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
