public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: khilman@deeprootsystems•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 00/13 v2] OMAP: Serial: Add omap-serial driver with platform support
Date: Wed, 22 Sep 2010 13:14:58 -0700	[thread overview]
Message-ID: <87k4mda62l.fsf@deeprootsystems.com> (raw)
In-Reply-To: <37596.172.24.137.131.1285168390.squirrel@dbdmail.itg.ti.com> (Govindraj R.'s message of "Wed, 22 Sep 2010 20:43:10 +0530 (IST)")

"Govindraj.R" <govindraj.raja@ti•com> writes:

> This patch series adds a serial driver to handle uarts on omap platforms.
> Currenlty omap-uarts are handled with 8250 driver, since updating
> this driver with omap specific features will over load
> the 8250 driver with all omap-specific data thus a new driver
> is added to configure and support features like
> dma, h/w, s/w flowcontrol for omap-uarts.
> Also the patch series updates various low level platform specific
> serial data to support omap-uarts with hwmod framework and adds support
> for uart4 on OMAP3630.
>
> v1 to v2 changes:
> ----------------
> 1) Incorporate timeout check
> 	http://www.mail-archive.com/linux-omap at vger.kernel.org/msg35106.html
> 2) Add wk_st, padconf etc for uart4
> 	http://www.mail-archive.com/linux-omap at vger.kernel.org/msg35105.html

3) All UARTs initialized for Zoom2/3

Also, please report platforms this was tested on, and what was tested.
You need to validate retention and off-mode during idle and suspend, as
well as enabling/disabling the UART sleep_timeout values via sysfs.

Thanks,

Kevin

      reply	other threads:[~2010-09-22 20:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 15:13 [PATCH 00/13 v2] OMAP: Serial: Add omap-serial driver with platform support Govindraj.R
2010-09-22 20:14 ` Kevin Hilman [this message]

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=87k4mda62l.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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