From mboxrd@z Thu Jan 1 00:00:00 1970 From: coelho@ti.com (Luciano Coelho) Date: Thu, 08 Mar 2012 21:05:47 +0200 Subject: [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4 In-Reply-To: References: <20120202093600.12509.35052.stgit@dusk> <87ty39cc7s.fsf@ti.com> <87sjhjaqyi.fsf@ti.com> <1331232433.18015.69.camel@cumari> Message-ID: <1331233547.18015.74.camel@cumari> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, 2012-03-08 at 11:55 -0700, Paul Walmsley wrote: > On Thu, 8 Mar 2012, Luciano Coelho wrote: > > > On Thu, 2012-03-08 at 10:27 -0800, Kevin Hilman wrote: > > > > > Are you enabling UART wakeups? > > > > > > They are disabled by default, so you need to: > > > > > > echo enabled > /sys/devices/platform/omap/omap_uart.2/tty/ttyO2/power/wakeup > > > > No, I was actually not enabling the UART wakeups. But I tried it now > > but it still doesn't work. :( > > You definitely need that. > > > I have no_console_suspend in bootargs. Without it, it didn't work with > > 3.2 either. > > If you want to use no_console_suspend -- which is not recommended -- then > you'll need > > http://www.spinics.net/lists/linux-omap/msg65786.html > > but best simply not to use no_console_suspend. Thanks, Paul! I was just chatting with Kevin about this on IRC. With your patch and no_console_suspend, it works. :) I needed no_console_suspend because it wouldn't work otherwise on <3.3-rc1. Now I tried a vanilla 3.3-rc5 without no_console_suspend and enabling the UART wakeup and it works fine! Thanks for your help, guys! -- Cheers, Luca.