public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Sourav Poddar <sourav.poddar@ti.com>
To: gregkh@linuxfoundation.org, tony@atomide.com,
	rmk+kernel@arm.linux.org.uk,
	linux-arm-kernel@lists.infradead.org
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-omap@vger.kernel.org, b-cousson@ti.com,
	Sourav Poddar <sourav.poddar@ti.com>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Felipe Balbi <balbi@ti.com>, Rajendra nayak <rnayak@ti.com>
Subject: [PATCH 0/2] omap serial fix.
Date: Mon, 18 Mar 2013 16:24:41 +0530	[thread overview]
Message-ID: <1363604081-11169-1-git-send-email-sourav.poddar@ti.com> (raw)

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.

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 10:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18 10:54 Sourav Poddar [this message]
2013-03-18 13:21 ` [PATCH 0/2] omap serial fix Sourav Poddar
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=1363604081-11169-1-git-send-email-sourav.poddar@ti.com \
    --to=sourav.poddar@ti.com \
    --cc=b-cousson@ti.com \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox