Hi Dave, On 12.08.2013 20:59, Dave Gerlach wrote: > On 08/11/2013 06:53 AM, Daniel Mack wrote: >> The problem I currently face is that I can't make the board resume, as >> neither UART0 nor GPIO0 seem to work as wakeup source. > > Did you apply the other patches that are mentioned besides Suman's > series? The board will hang while suspending without these. Yes. However, just to make sure you referenced the correct patches - on top of yours an Suman's set, I have: [PATCH 1/2] ARM: OMAP2+: hwmod: rt address space index for DT [PATCH 2/2] ARM: OMAP2+: hwmod: AM335x: fix cpgmac address space [PATCH 1/2] ARM: dts: add AM33XX EDMA support The last one seems somewhat unrelated though. However, I see an issue with the musb dsps glue. With the usb controller disabled in DT, I also had to remove the usb_otg_hs entry from am33xx_mod[] (pm33xx.c). When the usb controller is _enabled_, I get an instant NULL pointer exception due to a rather obvious bug. I'll send out a patch right now. When I send the board to suspend (with USB disabled), the power consumption drops significantly, and the output is: # echo mem > /sys/power/state [ 93.001937] PM: Syncing filesystems ... done. [ 93.033591] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 93.048532] Freezing remaining freezable tasks ... (elapsed 0.002 seconds) done. [ 93.059277] PM: Sending message for entering DeepSleep mode [ 93.085368] PM: suspend of devices complete after 15.070 msecs [ 93.096671] PM: late suspend of devices complete after 5.122 msecs [ 93.108853] PM: noirq suspend of devices complete after 5.647 msecs ... but traffic on UART0 won't cause a resume. I'll dig a little deeper now, but if you have any idea, please let me know. Thanks, Daniel -- 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
