Jean Pihet <jean.pihet@xxxxxxxxxxxxxx> writes: > l-o is currently broken wrt to suspend and idle. > Solutions are being worked on for the moment. > > Kevin, are there solutions available yet? The solution to your previous problem (ensuring runtime PM transitions work during system PM) is included in my pm-core branch, but is not yet the final solution. I've been disussing this issue with the runtime PM maintainers for a final solution. Until then, I will carry this in pm-core. 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. Of course, any help debugging these problems is appreciated. I will not get to debugging this until I catch up on the mailing list backlog. Kevin > On Wed, Nov 10, 2010 at 4:44 PM, Thomas Petazzoni > <thomas.petazzoni@xxxxxxxxxxxxxxxxxx> wrote: >> Hello, >> >> I've updated my tree to the last pm-core branch today (I'm at commit >> 42289e226ec996a13ab8a2aaef5ad9dda61ee57e), and I've built the >> omap2plus_defconfig with no change (except adding an initramfs). On my >> BeagleBoard, I enable the wakeup from UART >> in /sys/devices/platform/omap/omap-hsuart.2/tty/ttyO2/power/wakeup, >> then trigger suspend to RAM. It enters suspend to RAM, but then >> it doesn't wakeup when I send data through the UART. >> >> Is it a known problem, or is again a mistake on my side ? >> >> 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 majordomo@xxxxxxxxxxxxxxx >> More majordomo info at Âhttp://vger.kernel.org/majordomo-info.html >> > -- > 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 -- 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
