From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Santosh Shilimkar <santosh.shilimkar@ti.com>
Cc: linux-omap@vger.kernel.org, rnayak@ti.com,
linux@arm.linux.org.uk, paul@pwsan.com,
khilman@deeprootsystems.com, tony@atomide.com,
sourav.poddar@ti.com, vaibhav.bedia@ti.com,
linux-arm-kernel@lists.infradead.org, "Balbi,
Felipe" <balbi@ti.com>
Subject: Re: [PATCH 0/8] ARM; OMAP2+: hwmod and SERIAL: Remove sysc handling from driver
Date: Wed, 20 Feb 2013 15:32:22 +0530 [thread overview]
Message-ID: <51249F2E.6010404@ti.com> (raw)
In-Reply-To: <1361354272-18089-1-git-send-email-santosh.shilimkar@ti.com>
+ Felipe ( Sorry I missed you in CC list)
On Wednesday 20 February 2013 03:27 PM, Santosh Shilimkar wrote:
> 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.
>
> Patches has been tested on OMAP4430 SDP and OMAP5 EVM where the console
> sluggishness was observed without idle mode handling. CPUIDLE and
> suspend tested ok on these devices.
>
> Thanks to Vaibhav Bedia for testing on Beaglebone(AM33XX) with suspend and
> also the UART async wakeup from suspend.
>
> Thanks to Sourav Poddar for Beagle XM(OMAP3630) devices testing with
> retention and offmode in Idle and suspend for non-DT builds.
>
> Serial driver platform code still has one more function pointer
> left which is used to trigger io_ring(). This one needs some
> discussion with pincontrol driver folks on how to implement
> such a feature with generic pincontrol driver.
>
> Rajendra Nayak (4):
> ARM: OMAP2+: hwmod: Remove unused _HWMOD_WAKEUP_ENABLED flag
> ARM: OMAP2+: hwmod: Cleanup sidle/mstandby programming
> ARM: OMAP2+: hwmod: Always have OCP_SYSCONFIG.ENAWAKEUP enabled
> ARM: OMAP2+: hwmod: Add a new flag to handle SIDLE in SWSUP only in
> active
>
> Santosh Shilimkar (4):
> ARM: OMAP2+: hwmod-data: UART IP needs software control to manage
> sidle modes
> SERIAL: OMAP: Remove the slave idle handling from the driver
> ARM: OMAP2+: serial: Remove the un-used slave idle hooks
> ARM: OMAP2+: hwmod: Remove sysc slave idle and auto idle apis
>
> arch/arm/mach-omap2/omap_hwmod.c | 141 ++++----------------
> arch/arm/mach-omap2/omap_hwmod.h | 13 +-
> arch/arm/mach-omap2/omap_hwmod_2xxx_ipblock_data.c | 3 +
> arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 6 +
> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 4 +
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 6 +-
> arch/arm/mach-omap2/serial.c | 31 -----
> drivers/tty/serial/omap-serial.c | 23 ----
> 8 files changed, 50 insertions(+), 177 deletions(-)
>
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] ARM; OMAP2+: hwmod and SERIAL: Remove sysc handling from driver
Date: Wed, 20 Feb 2013 15:32:22 +0530 [thread overview]
Message-ID: <51249F2E.6010404@ti.com> (raw)
In-Reply-To: <1361354272-18089-1-git-send-email-santosh.shilimkar@ti.com>
+ Felipe ( Sorry I missed you in CC list)
On Wednesday 20 February 2013 03:27 PM, Santosh Shilimkar wrote:
> 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.
>
> Patches has been tested on OMAP4430 SDP and OMAP5 EVM where the console
> sluggishness was observed without idle mode handling. CPUIDLE and
> suspend tested ok on these devices.
>
> Thanks to Vaibhav Bedia for testing on Beaglebone(AM33XX) with suspend and
> also the UART async wakeup from suspend.
>
> Thanks to Sourav Poddar for Beagle XM(OMAP3630) devices testing with
> retention and offmode in Idle and suspend for non-DT builds.
>
> Serial driver platform code still has one more function pointer
> left which is used to trigger io_ring(). This one needs some
> discussion with pincontrol driver folks on how to implement
> such a feature with generic pincontrol driver.
>
> Rajendra Nayak (4):
> ARM: OMAP2+: hwmod: Remove unused _HWMOD_WAKEUP_ENABLED flag
> ARM: OMAP2+: hwmod: Cleanup sidle/mstandby programming
> ARM: OMAP2+: hwmod: Always have OCP_SYSCONFIG.ENAWAKEUP enabled
> ARM: OMAP2+: hwmod: Add a new flag to handle SIDLE in SWSUP only in
> active
>
> Santosh Shilimkar (4):
> ARM: OMAP2+: hwmod-data: UART IP needs software control to manage
> sidle modes
> SERIAL: OMAP: Remove the slave idle handling from the driver
> ARM: OMAP2+: serial: Remove the un-used slave idle hooks
> ARM: OMAP2+: hwmod: Remove sysc slave idle and auto idle apis
>
> arch/arm/mach-omap2/omap_hwmod.c | 141 ++++----------------
> arch/arm/mach-omap2/omap_hwmod.h | 13 +-
> arch/arm/mach-omap2/omap_hwmod_2xxx_ipblock_data.c | 3 +
> arch/arm/mach-omap2/omap_hwmod_33xx_data.c | 6 +
> arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 4 +
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 6 +-
> arch/arm/mach-omap2/serial.c | 31 -----
> drivers/tty/serial/omap-serial.c | 23 ----
> 8 files changed, 50 insertions(+), 177 deletions(-)
>
next prev parent reply other threads:[~2013-02-20 10:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 9:57 [PATCH 0/8] ARM; OMAP2+: hwmod and SERIAL: Remove sysc handling from driver Santosh Shilimkar
2013-02-20 9:57 ` Santosh Shilimkar
2013-02-20 9:57 ` [PATCH 1/8] ARM: OMAP2+: hwmod: Remove unused _HWMOD_WAKEUP_ENABLED flag Santosh Shilimkar
2013-02-20 9:57 ` Santosh Shilimkar
2013-03-31 1:58 ` Paul Walmsley
2013-03-31 1:58 ` Paul Walmsley
2013-03-31 2:27 ` Paul Walmsley
2013-03-31 2:27 ` Paul Walmsley
2013-02-20 9:57 ` [PATCH 2/8] ARM: OMAP2+: hwmod: Cleanup sidle/mstandby programming Santosh Shilimkar
2013-02-20 9:57 ` Santosh Shilimkar
2013-03-31 1:30 ` Paul Walmsley
2013-03-31 1:30 ` Paul Walmsley
2013-04-01 8:39 ` Rajendra Nayak
2013-04-01 8:39 ` Rajendra Nayak
2013-04-18 10:53 ` Rajendra Nayak
2013-04-18 10:53 ` Rajendra Nayak
2013-04-23 8:19 ` Paul Walmsley
2013-04-23 8:19 ` Paul Walmsley
2013-04-26 7:08 ` Rajendra Nayak
2013-04-26 7:08 ` Rajendra Nayak
2013-02-20 9:57 ` [PATCH 3/8] ARM: OMAP2+: hwmod: Always have OCP_SYSCONFIG.ENAWAKEUP enabled Santosh Shilimkar
2013-02-20 9:57 ` Santosh Shilimkar
2013-03-31 1:32 ` Paul Walmsley
2013-03-31 1:32 ` Paul Walmsley
2013-02-20 9:57 ` [PATCH 4/8] ARM: OMAP2+: hwmod: Add a new flag to handle SIDLE in SWSUP only in active Santosh Shilimkar
2013-02-20 9:57 ` Santosh Shilimkar
2013-02-20 10:02 ` Santosh Shilimkar [this message]
2013-02-20 10:02 ` [PATCH 0/8] ARM; OMAP2+: hwmod and SERIAL: Remove sysc handling from driver Santosh Shilimkar
2013-02-20 10:14 ` Russell King - ARM Linux
2013-02-20 10:14 ` Russell King - ARM Linux
2013-02-20 10:23 ` Santosh Shilimkar
2013-02-20 10:23 ` Santosh Shilimkar
2013-02-20 11:51 ` Russell King - ARM Linux
2013-02-20 11:51 ` Russell King - ARM Linux
2013-02-20 13:26 ` Santosh Shilimkar
2013-02-20 13:26 ` Santosh Shilimkar
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=51249F2E.6010404@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=balbi@ti.com \
--cc=khilman@deeprootsystems.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.