From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: Broken UART I/O wakeups on v3.4-rc4+
Date: Tue, 8 May 2012 13:12:03 -0700 [thread overview]
Message-ID: <20120508201203.GE5088@atomide.com> (raw)
In-Reply-To: <CAMrsUdL2ekriQfyM2QqK1h-Wv+r80sk38p8-NYnRJdd9x8UwCw@mail.gmail.com>
* Raja, Govindraj <govindraj.raja@ti•com> [120508 02:17]:
> On Tue, May 8, 2012 at 10:35 AM, Paul Walmsley <paul@pwsan•com> wrote:
> >
> > Govindraj,
> >
> > After your commit bce492c04ba8fc66a4ea0a52b181ba255daaaf54 ("ARM: OMAP2+:
> > UART: Fix incorrect population of default uart pads"), the kernel does not
> > return from static suspend when off-mode is enabled upon an incoming
> > serial character.
> >
> > The following steps reproduce the problem:
> >
> > echo 1 > /debug/pm_debug/enable_off_mode
> > echo mem > /sys/power/state
> > (send a serial character after suspend is entered)
> >
> > (N.B., on the BeagleBoard, the GPIO-connected "USER" button can be used to
> > wake the system at this point.)
> >
>
> The same is discussed in this thread as in here:
> http://www.spinics.net/lists/linux-omap/msg68659.html
>
> > Could you please fix this? ?We probably aren't too far from the v3.5 merge
> > window opening, so there isn't much time to fix it.
>
> okay, one possible solution is to probe pins dynamically
> and make rx wakeup capable which myself and Tony
> discussed and came up with this patch [1]
This would be good for the v3.5 merge window.
> or to add rx wakeup pad support for each board,
> based on uart used as console.
This should be still done too to avoid bootloader dependency
for setting up the serial ports.
Regards,
Tony
> [1]: http://www.spinics.net/lists/linux-omap/msg67822.html
prev parent reply other threads:[~2012-05-08 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 5:05 Broken UART I/O wakeups on v3.4-rc4+ Paul Walmsley
2012-05-08 9:13 ` Raja, Govindraj
2012-05-08 16:10 ` Paul Walmsley
2012-05-08 20:12 ` Tony Lindgren [this message]
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=20120508201203.GE5088@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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