Hello, On Wed, 10 Nov 2010 09:32:53 -0800 Kevin Hilman <khil...@deeprootsystems.com> wrote:
> The other problem that I'm aware of so far I've only seen on boards > with UART2 console (beagle, Overo, n900.) The printk messages that > warn of 'new worst case [de]activate latency" seem to be racing with > UART disable code. This makes sense, since this printk is printed to > the UART immediately after the UART is disabled, which is going to > cause problems with the current approach to UART pm we have in > mach-omap2/serial.c. I have not yet fully debugged this and found a > workaround. Even if I comment the "new worst case deactivate latency" message, my BeagleBoard still doesn't wake-up from suspend. Here's what I do: # echo enabled > /sys/class/tty/ttyO2/power/wakeup # echo mem > /sys/power/state [ 227.685028] PM: Syncing filesystems ... done. [ 227.699432] Freezing user space processes ... (elapsed 0.01 seconds) done. [ 227.725524] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done. [ 227.880706] PM: suspend of devices complete after 117.767 msecs [ 227.889160] PM: late suspend of devices complete after 2.136 msecs [ 227.895782] Disabling non-boot CPUs ... Any idea ? Thanks! Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com -- 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
