On Tue, Jun 22, 2010 at 7:31 AM, Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> wrote: > Mike Rapoport <mike@xxxxxxxxxxxxxx> writes: > >> Kevin Hilman wrote: >>> Peter Tseng <tsenpet09@xxxxxxxxx> writes: >>> >>>> I am seeing some discrepancies between the Overo (I believe I have a >>>> Water) and the Beagleboard (I have a Rev. B5) when resuming after a >>>> suspend to RAM. >>> >>> Not that it is much comfort, but I have the same problem on Overo but >>> don't see it on any other OMAP3 board. >>> >>> I have yet to debug this particular issue further. >> >> I had the same issue on CM-T35 and when I've disabled CONFIG_CPU_IDLE >> in the kernel configuration the issue disappeared. Maybe it'll be of >> some help. > > That just masks the problem by not auto-gating the UART clocks. OK, I think I finally figured out this problem. A similar thing was reported on the n900 recently and got me to thinking that it must be something fishy going on with the PER powerdomain since both n900 and Overo are using a UART2 console, and UART2 is in PER. Anyways, I just posted a patch[1] that should fix this. I'd appreciate if anyone else with an Overo could confirm that things are back to working as expected with CONFIG_CPU_IDLE. Thanks, Kevin [1] https://patchwork.kernel.org/patch/118709/ -- 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
