From: "Raja, Govindraj" <govindraj.raja@ti.com>
To: Kevin Hilman <khilman@ti.com>
Cc: linux-omap@vger.kernel.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Paul Walmsley <paul@pwsan.com>, Felipe Balbi <balbi@ti.com>
Subject: Re: [PATCH 0/3] OMAP2+: UART: Enable tx wakeup + remove cpu checks
Date: Thu, 22 Mar 2012 12:29:56 +0530 [thread overview]
Message-ID: <CAMrsUdLtC0iVk2qDDDXj2tteAzP5UQJXNvsCoJLEC9Yty2QjvQ@mail.gmail.com> (raw)
In-Reply-To: <87limurpsx.fsf@ti.com>
On Wed, Mar 21, 2012 at 7:58 PM, Kevin Hilman <khilman@ti.com> wrote:
> "Govindraj.R" <govindraj.raja@ti.com> writes:
>
>> From: "Govindraj.R" <govindraj.raja@ti.com>
>>
>> Based on Linux-OMAP tree uart branch.
>> (git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git
>> remotes/origin/uart)
>>
>> * Removes the cpu checks wherever possible and use version reg
>> for populating features and errata's
>> * enable tx wakeup available in wer reg for applicable
>> module revision's
>
> As this affects multiple SoCs, please report what SoCs it was tested on
> as well.
Sorry I for got to add that, here are details on what was tested.
1.) OMAP2430 SDP : Boot tested with uart1 as console.
2.) OMAP3430 SDP: Boot test, suspend/resume tests, retention off mode
(checking retention and off mode count
in cpu idle cases)
3.) OMAP3630 - Beagle XM: Boot test, suspend/resume tests, retention off mode
(checking retention and
off mode count in cpu idle cases)
4.) OMAP4430 - PANDA: Boot test, suspend/resume tests
5.) OMAP4460 - PANDA: Boot test.
--
Thanks,
Govindraj.R
>
> Thanks,
>
> Kevin
>
>> Govindraj.R (3):
>> OMAP2+: UART: Remove cpu checks for populating errata flags
>> OMAP2+: UART: enable tx wakeup bit for wer reg
>> OMAP2+: UART: replace omap34xx/omap4xx cpu checks with not omap24xx
>>
>> arch/arm/mach-omap2/serial.c | 13 +----
>> arch/arm/plat-omap/include/plat/omap-serial.h | 8 +++-
>> drivers/tty/serial/omap-serial.c | 71 ++++++++++++++++++++++++-
>> 3 files changed, 78 insertions(+), 14 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-03-22 7:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 10:24 [PATCH 0/3] OMAP2+: UART: Enable tx wakeup + remove cpu checks Govindraj.R
2012-03-21 10:24 ` [PATCH 1/3] OMAP2+: UART: Remove cpu checks for populating errata flags Govindraj.R
2012-03-27 21:03 ` Jon Hunter
2012-03-27 21:08 ` Jon Hunter
2012-03-28 11:09 ` Raja, Govindraj
2012-03-28 16:43 ` Jon Hunter
2012-03-29 7:35 ` Raja, Govindraj
2012-03-21 10:25 ` [PATCH 2/3] OMAP2+: UART: enable tx wakeup bit for wer reg Govindraj.R
2012-03-21 10:25 ` [PATCH 3/3] OMAP2+: UART: replace omap34xx/omap4xx cpu checks with not omap24xx Govindraj.R
2012-03-21 14:28 ` [PATCH 0/3] OMAP2+: UART: Enable tx wakeup + remove cpu checks Kevin Hilman
2012-03-22 6:59 ` Raja, Govindraj [this message]
2012-03-22 23:40 ` Paul Walmsley
2012-03-23 7:47 ` Raja, Govindraj
2012-04-05 11:24 ` Raja, Govindraj
2012-04-05 12:26 ` Alan Cox
2012-04-05 16:47 ` Greg KH
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=CAMrsUdLtC0iVk2qDDDXj2tteAzP5UQJXNvsCoJLEC9Yty2QjvQ@mail.gmail.com \
--to=govindraj.raja@ti.com \
--cc=balbi@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 \
--cc=paul@pwsan.com \
/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).