public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: coelho@ti.com (Luciano Coelho)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4
Date: Thu, 08 Mar 2012 21:05:47 +0200	[thread overview]
Message-ID: <1331233547.18015.74.camel@cumari> (raw)
In-Reply-To: <alpine.DEB.2.00.1203081153540.9551@utopia.booyaka.com>

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.

  reply	other threads:[~2012-03-08 19:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-02  9:38 [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4 Paul Walmsley
2012-02-02  9:38 ` [PATCH 1/2] ARM: OMAP2+: PM: share clkdms_setup() across OMAP2, 3, 4 Paul Walmsley
2012-02-02  9:38 ` [PATCH 2/2] ARM: OMAP2+: PM: share some suspend-related functions " Paul Walmsley
2012-02-02 11:25 ` [PATCH 0/2] ARM: OMAP2+: PM: code consolidation for 3.4 Shilimkar, Santosh
2012-02-02 18:38 ` Kevin Hilman
2012-02-02 18:40   ` Paul Walmsley
2012-02-02 20:29     ` Paul Walmsley
2012-03-08 12:21       ` Coelho, Luciano
2012-03-08 18:18         ` Paul Walmsley
2012-03-08 18:27         ` Kevin Hilman
2012-03-08 18:47           ` Luciano Coelho
2012-03-08 18:55             ` Paul Walmsley
2012-03-08 19:05               ` Luciano Coelho [this message]
2012-03-08 21:21                 ` Kevin Hilman
2012-03-09  6:15                   ` Luciano Coelho
2012-03-09 15:23                     ` Kevin Hilman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1331233547.18015.74.camel@cumari \
    --to=coelho@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox