From: Nishanth Menon <nm@ti.com>
To: Kevin Hilman <khilman@linaro.org>
Cc: Rajendra Nayak <rnayak@ti.com>,
linux-omap@vger.kernel.org, santosh.shilimkar@ti.com,
linux@arm.linux.org.uk, paul@pwsan.com, tony@atomide.com,
sourav.poddar@ti.com, vaibhav.bedia@ti.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/6] ARM; OMAP2+: hwmod and SERIAL: Remove sysc handling from driver
Date: Fri, 10 May 2013 09:02:00 -0500 [thread overview]
Message-ID: <20130510140200.GA11267@kahuna> (raw)
In-Reply-To: <87ppxhxixu.fsf@linaro.org>
On 11:09-20130426, Kevin Hilman wrote:
> Rajendra Nayak <rnayak@ti.com> writes:
>
> [...]
>
> > OMAP UART IP needs manual idle modes based on functional state of the
> > IP. Currently this is handled by the driver with function pointers
> > implemented in platform code.
> >
> > This however breaks in case of device tree because of missing
> > idle handling.
> >
> > The series tries to address the issue and tries to remove complete
> > sysc handling from serial driver.
>
> Other than the minor nit about the order of the series for bisect,
>
> Reviewed-by: Kevin Hilman <khilman@linaro.org>
>
> Also tested this on OMAP4/Panda where I was having the sluggish console
> issues using DT boot, and and can confirm that this fixes the problem:
>
> Tested-by: Kevin Hilman <khilman@linaro.org> # OMAP4/Panda
>
I saw the same let of console sluggishness on SDP4430, Panda, Panda-ES
as well on latest linus master.
For reference, I have rebased the series to latest master and fixes the
sequencing:
https://github.com/nmenon/linux-2.6-playground/commits/push/uart-fixes-sidle-3.10
based on:
master 70eba42 Merge tag 'please-pull-pstore' of git://git.kernel.org/pub/scm/linux/kernel/git/aegl/linux
Rajendra,
Would you be able to repost this series so that we can get this into
3.10-rc2+?
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2013-05-10 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 10:54 [PATCH v2 0/6] ARM; OMAP2+: hwmod and SERIAL: Remove sysc handling from driver Rajendra Nayak
2013-04-26 10:54 ` [PATCH v2 1/6] ARM: OMAP2+: hwmod: Fix sidle programming in _enable_sysc()/_idle_sysc() Rajendra Nayak
2013-04-26 10:54 ` [PATCH v2 2/6] ARM: OMAP2+: hwmod: Add a new flag to handle SIDLE in SWSUP only in active Rajendra Nayak
2013-04-26 10:54 ` [PATCH v2 3/6] ARM: OMAP2+: hwmod-data: UART IP needs software control to manage sidle modes Rajendra Nayak
2013-04-26 10:54 ` [PATCH v2 4/6] SERIAL: OMAP: Remove the slave idle handling from the driver Rajendra Nayak
2013-04-26 18:05 ` Kevin Hilman
2013-04-26 10:54 ` [PATCH v2 5/6] ARM: OMAP2+: serial: Remove the un-used slave idle hooks Rajendra Nayak
2013-04-26 10:54 ` [PATCH v2 6/6] ARM: OMAP2+: hwmod: Remove sysc slave idle and auto idle apis Rajendra Nayak
2013-04-26 18:09 ` [PATCH v2 0/6] ARM; OMAP2+: hwmod and SERIAL: Remove sysc handling from driver Kevin Hilman
2013-05-10 14:02 ` Nishanth Menon [this message]
2013-05-15 15:00 ` Rajendra Nayak
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=20130510140200.GA11267@kahuna \
--to=nm@ti.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=paul@pwsan.com \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=sourav.poddar@ti.com \
--cc=tony@atomide.com \
--cc=vaibhav.bedia@ti.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).