linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sourav.poddar@ti.com (Sourav Poddar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] omap serial fix.
Date: Mon, 18 Mar 2013 18:51:29 +0530	[thread overview]
Message-ID: <514714D9.1040702@ti.com> (raw)
In-Reply-To: <1363604081-11169-1-git-send-email-sourav.poddar@ti.com>

Hi,
On Monday 18 March 2013 04:24 PM, Sourav Poddar wrote:
> The first patch is a rearrangement of a macro "OMAP_MAX_HSUART_PORTS"
> to a header file so that it can be used in other file.
> The second patch fixes the wakeup from uart issue while using "no_console_suspend" in the
> bootargs.
>
> These patches are developed on 3.8 custom kernel containing omap5 supend/resume support.
>
Adding a bit more information,
These patches are not omap5 specific and required for omap4 also.
For OMAP5 testing purpose, I used 3.8 based internal tree.

First patch gets applied cleanly on 3.9-rc3.
Resending the second patch rebased on 3.9-rc3, as there is a small
merge conflict.
> Cc: Santosh Shilimkar<santosh.shilimkar@ti.com>
> Cc: Felipe Balbi<balbi@ti.com>
> Cc: Rajendra nayak<rnayak@ti.com>
>
> Sourav Poddar (2):
>    driver: serial-omap: move max uart count into generic header file.
>    arm: mach-omap2: prevent UART console idle on suspend while using
>      "no_console_suspend"
>
>   arch/arm/mach-omap2/omap_device.c         |   36 ++++++++++++++++++++++++++++-
>   drivers/tty/serial/omap-serial.c          |    2 -
>   include/linux/platform_data/serial-omap.h |    1 +
>   3 files changed, 36 insertions(+), 3 deletions(-)
>

  reply	other threads:[~2013-03-18 13:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18 10:54 [PATCH 0/2] omap serial fix Sourav Poddar
2013-03-18 13:21 ` Sourav Poddar [this message]
2013-03-19  6:54 ` 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=514714D9.1040702@ti.com \
    --to=sourav.poddar@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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).