All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: alan@linux.intel.com, jslaby@suse.cz, grant.likely@secretlab.ca,
	rob.herring@calxeda.com, devicetree-discuss@lists.ozlabs.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-serial@vger.kernel.org, linux-tegra@vger.kernel.org,
	swarren@wwwdotorg.org
Subject: Re: [PATCH] serial: tegra: add serial driver
Date: Mon, 17 Dec 2012 07:13:09 -0800	[thread overview]
Message-ID: <20121217151309.GA15665@kroah.com> (raw)
In-Reply-To: <1355746249-15347-1-git-send-email-ldewangan@nvidia.com>

On Mon, Dec 17, 2012 at 05:40:49PM +0530, Laxman Dewangan wrote:
> Nvidia's Tegra has multiple uart controller which supports:
> - APB dma based controller fifo read/write.
> - End Of Data interrupt in incoming data to know whether end
>   of frame achieve or not.
> - Hw controlled RTS and CTS flow control to reduce SW overhead.
> 
> Add serial driver to use all above feature.
> 
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
>  .../bindings/serial/nvidia,serial-tegra.txt        |   26 +
>  drivers/tty/serial/Kconfig                         |   14 +
>  drivers/tty/serial/Makefile                        |    1 +
>  drivers/tty/serial/serial_tegra.c                  | 1398 ++++++++++++++++++++
>  include/linux/serial_tegra.h                       |   33 +

This file should be in include/linux/platform_data/, right?

thanks,

greg k-h

  reply	other threads:[~2012-12-17 15:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 12:10 [PATCH] serial: tegra: add serial driver Laxman Dewangan
2012-12-17 12:10 ` Laxman Dewangan
2012-12-17 15:13 ` Greg KH [this message]
2012-12-17 15:24 ` Rob Herring
2012-12-17 21:30   ` Stephen Warren
2012-12-17 17:10 ` Grant Likely
2012-12-17 17:10   ` Grant Likely
2012-12-17 21:31   ` Stephen Warren
2012-12-19 13:01     ` Grant Likely
2012-12-19 14:15       ` Laxman Dewangan
     [not found]         ` <50D1CC07.6070506-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-19 16:58           ` Stephen Warren
2012-12-19 16:58             ` Stephen Warren
2012-12-20  1:09             ` Grant Likely
2012-12-17 18:23 ` Alan Cox
2012-12-17 18:23   ` Alan Cox
     [not found] ` <1355746249-15347-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-12-17 21:36   ` Stephen Warren
2012-12-17 21:36     ` Stephen Warren
     [not found]     ` <50CF9043.8030308-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-17 21:58       ` Mitch Bradley
2012-12-17 21:58         ` Mitch Bradley
     [not found]         ` <50CF9580.4050300-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2012-12-17 22:04           ` Stephen Warren
2012-12-17 22:04             ` Stephen Warren
     [not found]             ` <50CF96D4.6010705-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-12-17 22:17               ` Mitch Bradley
2012-12-17 22:17                 ` Mitch Bradley
2012-12-19 13:03                 ` Grant Likely
2012-12-17 21:55 ` Stephen Warren

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=20121217151309.GA15665@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alan@linux.intel.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=jslaby@suse.cz \
    --cc=ldewangan@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@wwwdotorg.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 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.