From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-serial@vger.kernel.org,
Govindraj Raja <govindraj.raja@ti.com>
Subject: Re: [GIT PULL] OMAP: UART cleanup and runtime PM conversion for v3.3
Date: Fri, 16 Dec 2011 10:24:16 -0800 [thread overview]
Message-ID: <20111216182416.GD32251@atomide.com> (raw)
In-Reply-To: <878vmeodsx.fsf@ti.com>
* Kevin Hilman <khilman@ti.com> [111214 16:22]:
> Tony,
>
> Please pull the OMAP UART cleanup and conversion to runtime PM. I had
> to rebase it onto your soc branch due to the serial.c changes there.
>
> This includes changes to drivers/tty/serial/omap-serial.c and those
> changes have Acks from Greg KH and Alan Cox and I got the OK from them
> to merge this all together via the OMAP tree.
>
> Thanks to Govindraj for his persistence with this series.
>
> Boot tested on 2420/n810, 4430/Blaze, 4430/Panda
> Additional PM testing on 3430/n900, 3530/Overo, 3630/Zoom3.
>
> NOTE: while normal UART behavior works fine with this series, including
> suspend/resume, in order for wakeups from runtime PM to work, this
> series depends on the PRCM IRQ chaining series from Tero and the
> the new hwmod init state from Rajendra[1]. However, since runtime
> PM is disabled by default for the UARTs, they will behave normally
> even without those dependencies.
>
> Kevin
>
> [1] http://marc.info/?l=linux-omap&m=132187766930901&w=2
Thanks pulling this into uart branch.
Regards,
Tony
prev parent reply other threads:[~2011-12-16 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 0:53 [GIT PULL] OMAP: UART cleanup and runtime PM conversion for v3.3 Kevin Hilman
2011-12-16 18:24 ` 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=20111216182416.GD32251@atomide.com \
--to=tony@atomide.com \
--cc=govindraj.raja@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.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).