From: Sourav Poddar <sourav.poddar@ti.com>
To: Sourav Poddar <sourav.poddar@ti.com>
Cc: gregkh@linuxfoundation.org, tony@atomide.com,
rmk+kernel@arm.linux.org.uk, khilman@linaro.org,
linux-serial@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Felipe Balbi <balbi@ti.com>, Rajendra nayak <rnayak@ti.com>
Subject: Re: [PATCHv5 0/3] Serial fixes
Date: Sat, 27 Apr 2013 01:51:39 +0530 [thread overview]
Message-ID: <517AE1D3.5050702@ti.com> (raw)
In-Reply-To: <1367006686-3720-1-git-send-email-sourav.poddar@ti.com>
On Saturday 27 April 2013 01:34 AM, Sourav Poddar wrote:
> Hi,
>
> This patch series contains fixes around the issue that
> the console UART should not idled on suspend while using
> "no_console_suspend" in bootargs.
>
> The approach thought of is to modify the serial core/serial driver to bypass
> runtime PM if the UART in contention is a console and we are using "no_console_suspend"
> in our bootargs.
>
> There were discussions about how to handle "no_idle_on_suspend" issue and all the
> discussions are as follows:
> https://lkml.org/lkml/2013/4/5/239
> https://lkml.org/lkml/2013/4/2/350
> https://lkml.org/lkml/2013/3/18/199
> https://lkml.org/lkml/2013/3/18/295
> Due to the amount of change in approach, I am posting
> this as a new series.
>
> v4->v5
> 1. Add comments
> 2. Formatting.
>
> v3->v4
> 1. check for console in runtime api.
>
> v2->v3
> 1. Use "-EBUSY" for no_console_suspend case
> 2. Bypass runtime PM only during suspend
> 3. Improve the commit log based on community suggestion.
>
> v1->v2
> 1. Remove the prepare/complete callback.
> 2. Adapt runtime PM callback to deal with the issue.
> 3. Fold patch(1,2) of previous series into 1.
> 4. Reordered the patch.
> 5. Change $subject and chage log for few patches.
>
> Cc: Santosh Shilimkar<santosh.shilimkar@ti.com>
> Cc: Felipe Balbi<balbi@ti.com>
> Cc: Rajendra nayak<rnayak@ti.com>
>
> Test info
> Omap4430sdp:
> - Tested wakeup from UART after suspend for dt and non dt case.
> Omap5430evm:
> - Tested wakeup from UART after suspend for dt case.
>
> These patches were the part of the bigger series[1]. Breaking them into
> two relevant series as they go through the different tree.
>
> [1]: http://lkml.org/lkml/2013/4/26/274
>
> This patches are based on 3.9-rc8
>
> The following changes since commit 824282ca7d250bd7c301f221c3cd902ce906d731:
>
> Merge branch 'upstream' of git://git.linux-mips.org/pub/scm/ralf/upstream-linus (2013-04-22 15:00:59 -0700)
>
> are available in the git repository at:
>
> git://gitorious.org/linux-connectivity/linux-connectivity.git serial_fix
>
> Sourav Poddar (2):
> driver: tty: serial: Move "uart_console" def to core header file.
> driver: serial: omap: prevent runtime PM for "no_console_suspend"
>
> drivers/tty/serial/mpc52xx_uart.c | 10 ----------
> drivers/tty/serial/omap-serial.c | 34 +++++++++++++++++++++++++++++++++-
> drivers/tty/serial/serial_core.c | 6 ------
> include/linux/serial_core.h | 7 +++++++
> 4 files changed, 40 insertions(+), 17 deletion
Discard this cover..resend the cover with correct subject.
WARNING: multiple messages have this Message-ID (diff)
From: Sourav Poddar <sourav.poddar@ti.com>
To: Sourav Poddar <sourav.poddar@ti.com>
Cc: <gregkh@linuxfoundation.org>, <tony@atomide.com>,
<rmk+kernel@arm.linux.org.uk>, <khilman@linaro.org>,
<linux-serial@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Felipe Balbi <balbi@ti.com>, Rajendra nayak <rnayak@ti.com>
Subject: Re: [PATCHv5 0/3] Serial fixes
Date: Sat, 27 Apr 2013 01:51:39 +0530 [thread overview]
Message-ID: <517AE1D3.5050702@ti.com> (raw)
In-Reply-To: <1367006686-3720-1-git-send-email-sourav.poddar@ti.com>
On Saturday 27 April 2013 01:34 AM, Sourav Poddar wrote:
> Hi,
>
> This patch series contains fixes around the issue that
> the console UART should not idled on suspend while using
> "no_console_suspend" in bootargs.
>
> The approach thought of is to modify the serial core/serial driver to bypass
> runtime PM if the UART in contention is a console and we are using "no_console_suspend"
> in our bootargs.
>
> There were discussions about how to handle "no_idle_on_suspend" issue and all the
> discussions are as follows:
> https://lkml.org/lkml/2013/4/5/239
> https://lkml.org/lkml/2013/4/2/350
> https://lkml.org/lkml/2013/3/18/199
> https://lkml.org/lkml/2013/3/18/295
> Due to the amount of change in approach, I am posting
> this as a new series.
>
> v4->v5
> 1. Add comments
> 2. Formatting.
>
> v3->v4
> 1. check for console in runtime api.
>
> v2->v3
> 1. Use "-EBUSY" for no_console_suspend case
> 2. Bypass runtime PM only during suspend
> 3. Improve the commit log based on community suggestion.
>
> v1->v2
> 1. Remove the prepare/complete callback.
> 2. Adapt runtime PM callback to deal with the issue.
> 3. Fold patch(1,2) of previous series into 1.
> 4. Reordered the patch.
> 5. Change $subject and chage log for few patches.
>
> Cc: Santosh Shilimkar<santosh.shilimkar@ti.com>
> Cc: Felipe Balbi<balbi@ti.com>
> Cc: Rajendra nayak<rnayak@ti.com>
>
> Test info
> Omap4430sdp:
> - Tested wakeup from UART after suspend for dt and non dt case.
> Omap5430evm:
> - Tested wakeup from UART after suspend for dt case.
>
> These patches were the part of the bigger series[1]. Breaking them into
> two relevant series as they go through the different tree.
>
> [1]: http://lkml.org/lkml/2013/4/26/274
>
> This patches are based on 3.9-rc8
>
> The following changes since commit 824282ca7d250bd7c301f221c3cd902ce906d731:
>
> Merge branch 'upstream' of git://git.linux-mips.org/pub/scm/ralf/upstream-linus (2013-04-22 15:00:59 -0700)
>
> are available in the git repository at:
>
> git://gitorious.org/linux-connectivity/linux-connectivity.git serial_fix
>
> Sourav Poddar (2):
> driver: tty: serial: Move "uart_console" def to core header file.
> driver: serial: omap: prevent runtime PM for "no_console_suspend"
>
> drivers/tty/serial/mpc52xx_uart.c | 10 ----------
> drivers/tty/serial/omap-serial.c | 34 +++++++++++++++++++++++++++++++++-
> drivers/tty/serial/serial_core.c | 6 ------
> include/linux/serial_core.h | 7 +++++++
> 4 files changed, 40 insertions(+), 17 deletion
Discard this cover..resend the cover with correct subject.
next prev parent reply other threads:[~2013-04-26 20:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 20:04 [PATCHv5 0/3] Serial fixes Sourav Poddar
2013-04-26 20:04 ` Sourav Poddar
2013-04-26 20:04 ` [PATCHv5 1/2] driver: tty: serial: Move "uart_console" def to core header file Sourav Poddar
2013-04-26 20:04 ` Sourav Poddar
[not found] ` <87vc79uezo.fsf@linaro.org>
2013-04-26 22:18 ` Greg KH
2013-05-15 14:43 ` Sourav Poddar
2013-05-15 14:43 ` Sourav Poddar
2013-05-15 14:57 ` Greg KH
2013-05-15 14:57 ` Sourav Poddar
2013-05-15 14:57 ` Sourav Poddar
2013-05-15 15:43 ` Sourav Poddar
2013-05-15 15:43 ` Sourav Poddar
2013-04-26 20:04 ` [PATCHv5 2/2] driver: serial: omap: prevent runtime PM for "no_console_suspend" Sourav Poddar
2013-04-26 20:04 ` Sourav Poddar
2013-04-26 20:21 ` Sourav Poddar [this message]
2013-04-26 20:21 ` [PATCHv5 0/3] Serial fixes Sourav Poddar
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=517AE1D3.5050702@ti.com \
--to=sourav.poddar@ti.com \
--cc=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=rnayak@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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.