From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Manish Badarkhe <badarkhe.manish@gmail.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
grant.likely@secretlab.ca, rob.herring@calxeda.com,
linux-doc@vger.kernel.org, devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
spi-devel-general@lists.sourceforge.net,
linux-tegra@vger.kernel.org, swarren@nvidia.com
Subject: Re: [PATCH V3] spi: tegra114: add spi driver
Date: Fri, 22 Feb 2013 18:02:26 +0000 [thread overview]
Message-ID: <20130222180226.GC19796@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAKDJKT5yngpZQC-ZvHSaKeBVHW97wo4QwLSXQ4KsVWCs5J1YKg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
On Fri, Feb 22, 2013 at 07:59:11PM +0530, Manish Badarkhe wrote:
> On Fri, Feb 22, 2013 at 6:07 PM, Laxman Dewangan <ldewangan@nvidia.com> wrote:
> > Add SPI driver for NVIDIA's Tegra114 SPI controller. This controller
> > is different than the older SoCs SPI controller in internal design as
> > well as register interface.
> >
> > This driver supports the:
> > - non DMA based transfer for smaller transfer i.e. less than FIFO depth.
> > - APB DMA based transfer for lager transfer i.e. more than FIFO depth.
>
> s/lager/larger
>
> > - Clock gating through runtime PM callbacks.
> > - registration through DT only.
Delete unneeded context from your replies, we shouldn't need to page
through the entire patch because you've noticed a spelling error...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-02-22 18:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 12:37 [PATCH V3] spi: tegra114: add spi driver Laxman Dewangan
2013-02-22 12:37 ` Laxman Dewangan
[not found] ` <1361536659-23225-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2013-02-22 14:29 ` Manish Badarkhe
2013-02-22 14:29 ` Manish Badarkhe
2013-02-22 18:02 ` Mark Brown [this message]
2013-03-03 12:49 ` Manish Badarkhe
[not found] ` <CAKDJKT5yngpZQC-ZvHSaKeBVHW97wo4QwLSXQ4KsVWCs5J1YKg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-02 23:09 ` Grant Likely
2013-03-02 23:09 ` Grant Likely
2013-03-28 11:38 ` Laxman Dewangan
2013-03-28 11:38 ` Laxman Dewangan
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=20130222180226.GC19796@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=badarkhe.manish@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=swarren@nvidia.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.