From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP: UART: don't resume UARTs that are not enabled.
Date: Wed, 24 Nov 2010 14:35:16 -0800 [thread overview]
Message-ID: <20101124223516.GX31536@atomide.com> (raw)
In-Reply-To: <1290631720.15533.30.camel@eowin>
* Felipe Balbi <me@felipebalbi.com> [101124 12:39]:
> Hi,
>
> On Wed, 2010-11-24 at 11:09 -0800, Kevin Hilman wrote:
> > Add additional check to omap_uart_resume_idle() so that only
> > enabled (specfically, idle-enabled) UARTs are allowed to resume.
>
> typo: specifically
Also, without this patch, system with PM enabled hangs in
cases where only one serial port is initialized instead of
all of them. So I'll queue it as a fix during the -rc cycle.
Regards,
Tony
prev parent reply other threads:[~2010-11-24 22:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 19:09 [PATCH] OMAP: UART: don't resume UARTs that are not enabled Kevin Hilman
2010-11-24 20:48 ` Felipe Balbi
2010-11-24 22:35 ` 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=20101124223516.GX31536@atomide.com \
--to=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).