On Friday 08 June 2012 06:46 PM, Rajendra Nayak wrote:
On Friday 08 June 2012 06:35 PM, Tero Kristo wrote:
On Fri, 2012-06-08 at 17:55 +0530, Rajendra Nayak wrote:
On Friday 08 June 2012 04:26 PM, Tony Lindgren wrote:
* Rajendra Nayak<rnayak@xxxxxx> [120608 03:40]:
Hi,
I don;t seem to be able to get suspend to work on 3.5-rc1 on
my 4430 panda. I am not sure if its UART wakeups that are
an issue or suspend itself is broken.
Is there anything more than setting
'/sys/devices/platform/omap_uart.2/tty/ttyO2/power/wakeup'
to 'enabled' that I need to do to get UART to be wakeup capable?
3.4 major works just fine for me.
Can you try with the fixes branch that Olof just merged?
I tried merging the fixes branch on 3.5-rc1 as well as latest
mainline and both didn't work.
If it's the UART wake-up events, there's a patch that should
help.
Tony
The patch referenced here helps:
http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg69596.html
DSS crashes during wakeup from suspend.
great, thats what I found too with no_console_suspend, didn't know
a fix already exists. Thanks.
The patch above seems to fix suspend on 4430, but on my 4460 ES1.1
panda, I still see its broken..
# echo enabled > /sys/devices/platform/omap_uart.2/tty/ttyO2/power/wakeup
# echo mem > /sys/power/state
[ 6.549285] PM: Syncing filesystems ... done.
[ 6.581695] Freezing user space processes ... (elapsed 0.02 seconds)
done.
[ 6.612823] Freezing remaining freezable tasks ... (elapsed 0.02
seconds) done.
[ 6.674102] PM: suspend of devices complete after 51.391 msecs
[ 6.682006] PM: late suspend of devices complete after 1.739 msecs
[ 6.691650] PM: noirq suspend of devices complete after 3.143 msecs
[ 6.698272] Disabling non-boot CPUs ...
[ 6.705993] CPU1: shutdown
[ 7.298797] Successfully put all powerdomains to target state
[ 7.304992] Enabling non-boot CPUs ... *<---- hang*
..anyone knows of any more fixes going around?
regards,
Rajendra
--
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
