linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 3/3] ARM: tegra: document use of standard DMA DT bindings
Date: Mon, 25 Nov 2013 15:25:44 -0700	[thread overview]
Message-ID: <5293CE68.3000801@wwwdotorg.org> (raw)
In-Reply-To: <11843948.6MmkNU7Gku@wuerfel>

On 11/25/2013 03:07 PM, Arnd Bergmann wrote:
> On Monday 25 November 2013 15:06:01 Stephen Warren wrote:
>>    See ../reset/reset.txt for details.
>>  - reset-names : Must include the following entries:
>>    - dma
>> +- #iommu-cells : Must be <1>. This dictates the length of DMA specifiers in
>> +  client nodes' dmas properties. The specifier represents the DMA request
>> +  select value for the peripheral. For more details, consult the Tegra TRM's
>> +  documentation of the APB DMA channel control register REQ_SEL field.
>>  
>>  Examples:
>>  
>> @@ -36,4 +40,5 @@ apbdma: dma at 6000a000 {
>>         clocks = <&tegra_car 34>;
>>         resets = <&tegra_car 34>;
>>         reset-names = "dma";
>> +       #iommu-cells = <1>;
> 
> s/iommu-cells/dma-cells/

Thanks.

Uggh. I know you pointed that out before, and I fixed it. I guess I
screwed up a rebase somewhere:-(

      reply	other threads:[~2013-11-25 22:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25 22:05 [PATCH V2 0/3] ARM: tegra: use common reset and DMA bindings Stephen Warren
2013-11-25 22:05 ` [PATCH V2 1/3] ARM: tegra: add missing clock documentation to DT bindings Stephen Warren
2013-11-25 22:06 ` [PATCH V2 2/3] ARM: tegra: document reset properties in " Stephen Warren
2013-11-25 22:06 ` [PATCH V2 3/3] ARM: tegra: document use of standard DMA " Stephen Warren
2013-11-25 22:07   ` Arnd Bergmann
2013-11-25 22:25     ` Stephen Warren [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=5293CE68.3000801@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=linux-arm-kernel@lists.infradead.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 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).