From: Richard Zhao <rizhao@nvidia.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Ian Campbell <ian.campbell@citrix.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Mark Rutland <Mark.Rutland@arm.com>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"vinod.koul@intel.com" <vinod.koul@intel.com>,
"djbw@fb.com" <djbw@fb.com>
Subject: Re: [PATCH 3/9] spi: tegra114: move to generic dma DT binding
Date: Tue, 30 Jul 2013 11:15:36 +0800 [thread overview]
Message-ID: <20130730031536.GK15855@rizhao-lap> (raw)
In-Reply-To: <51F2CF53.30002@wwwdotorg.org>
On Sat, Jul 27, 2013 at 03:34:43AM +0800, Stephen Warren wrote:
> (Stripping CC list a bit)
>
> On 07/23/2013 10:09 PM, Richard Zhao wrote:
> > - driver: remove use of nvidia,dma-request-selector
> > use dma_request_slave_channel to request channel
> > - if dmas/dma-names are missing, it still supports cpu based transfer
> > - update binding doc and specify dmas/dma-names properties as optional
>
> I'll simply repeat the comments I already made downstream:
>
> Most commit messages aren't written as bullet points.
Alright, I'll change it. (Personally I like bullet points).
> This might be
> better written as:
>
> ----------
> Convert the Tegra114 SPI driver to support the standard DMA device-tree
> bindings.
>
> Note that DMA mode is optional; if the DT properties required to support
> DMA are missing, then the driver will fall back to pure CPU operation.
> ----------
>
> > diff --git a/Documentation/devicetree/bindings/spi/nvidia,tegra114-spi.txt b/Documentation/devicetree/bindings/spi/nvidia,tegra114-spi.txt
>
> > +Optional properties:
> > +- dmas : The Tegra DMA controller's phandle and request selector for
> > + this SPI controller.
> > +- dma-names : Should be "rx-tx".
>
> This should reference dma.txt which defines the DMA DT bindings. How about:
>
> ----------
> Optional properties:
> - dmas, dma-names : The DMA channel to use for DMA-mode operation. See
> dma.txt for the definition of these properties. A single entry named
> "rx-tx" must be specified.
> ----------
Ok. but how about replace "DMA channel" with "DMA request"?
Thanks
Richard
next prev parent reply other threads:[~2013-07-30 3:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 4:09 [PATCH 0/9] ARM: tegra: move to generic DMA DT binding Richard Zhao
2013-07-24 4:09 ` [PATCH 1/9] ARM: dts: add generic DMA DT binding for tegra apbdma Richard Zhao
2013-07-24 4:09 ` [PATCH 2/9] dma: tegra20-apbdma: move to generic device tree bindings Richard Zhao
2013-07-24 4:09 ` [PATCH 3/9] spi: tegra114: move to generic dma DT binding Richard Zhao
2013-07-26 19:34 ` Stephen Warren
2013-07-30 3:15 ` Richard Zhao [this message]
2013-07-30 16:44 ` Stephen Warren
2013-07-24 4:09 ` [PATCH 4/9] spi: tegra20-slink: " Richard Zhao
2013-07-24 4:09 ` [PATCH 5/9] spi: tegra20-sflash: " Richard Zhao
2013-07-24 4:09 ` [PATCH 6/9] serial: tegra: " Richard Zhao
2013-07-26 19:39 ` Stephen Warren
2013-07-26 19:41 ` Stephen Warren
[not found] ` <51F2D063.5010505-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-07-30 3:31 ` Richard Zhao
2013-07-30 16:46 ` Stephen Warren
2013-07-31 3:45 ` Richard Zhao
2013-07-31 21:32 ` Stephen Warren
[not found] ` <51F98275.6020906-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-08-01 3:30 ` Richard Zhao
2013-08-01 3:45 ` Stephen Warren
2013-07-24 4:10 ` [PATCH 7/9] ASoC: tegra: move to generic DMA " Richard Zhao
2013-07-24 6:58 ` Lars-Peter Clausen
2013-07-24 4:10 ` [PATCH 8/9] ARM: dts: tegra: remove legacy nvidia,dma-request-selector properties Richard Zhao
2013-07-24 4:10 ` [PATCH 9/9] dma: tegra20-apbdma: remove legacy nvidia,dma-request-selector support Richard Zhao
2013-07-26 19:25 ` [PATCH 0/9] ARM: tegra: move to generic DMA DT binding 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=20130730031536.GK15855@rizhao-lap \
--to=rizhao@nvidia.com \
--cc=Mark.Rutland@arm.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree@vger.kernel.org \
--cc=djbw@fb.com \
--cc=ian.campbell@citrix.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=swarren@wwwdotorg.org \
--cc=vinod.koul@intel.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;
as well as URLs for NNTP newsgroup(s).