ac100 team mailing list archive
-
ac100 team
-
Mailing list archive
-
Message #01184
Re: [PATCH 00/31] ARM: tegra: use common reset and DMA bindings
-
To:
Arnd Bergmann <arnd@xxxxxxxx>, linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
-
From:
Stephen Warren <swarren@xxxxxxxxxxxxx>
-
Date:
Wed, 20 Nov 2013 09:45:17 -0700
-
Cc:
Mark Rutland <mark.rutland@xxxxxxx>, alsa-devel@xxxxxxxxxxxxxxxx, Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>, Wolfram Sang <wsa@xxxxxxxxxxxxx>, David Airlie <airlied@xxxxxxxx>, linux-pci@xxxxxxxxxxxxxxx, dri-devel@xxxxxxxxxxxxxxxxxxxxx, Bjorn Helgaas <bhelgaas@xxxxxxxxxx>, linux-i2c@xxxxxxxxxxxxxxx, ac100@xxxxxxxxxxxxxxxxxxx, devel@xxxxxxxxxxxxxxxxxxxx, Stephen Warren <swarren@xxxxxxxxxx>, Mike Turquette <mturquette@xxxxxxxxxx>, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>, linux-serial@xxxxxxxxxxxxxxx, linux-input@xxxxxxxxxxxxxxx, treding@xxxxxxxxxx, devicetree@xxxxxxxxxxxxxxx, Pawel Moll <pawel.moll@xxxxxxx>, Ian Campbell <ijc+devicetree@xxxxxxxxxxxxxx>, Julian Andres Klode <jak@xxxxxxxxxxxxx>, Rob Herring <rob.herring@xxxxxxxxxxx>, Mark Brown <broonie@xxxxxxxxxx>, linux-tegra@xxxxxxxxxxxxxxx, Terje Bergström <tbergstrom@xxxxxxxxxx>, Dan Williams <dan.j.williams@xxxxxxxxx>, Dmitry Torokhov <dtor@xxxxxxx>, pdeschrijver@xxxxxxxxxx, linux-usb@xxxxxxxxxxxxxxx, Liam Girdwood <lgirdwood@xxxxxxxxx>, linux-spi@xxxxxxxxxxxxxxx, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<201311201637.36733.arnd@arndb.de>
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
On 11/20/2013 08:37 AM, Arnd Bergmann wrote:
> On Friday 15 November 2013, Stephen Warren wrote:
>> This series implements a common reset framework driver for Tegra, and
>> updates all relevant Tegra drivers to use it. It also removes the custom
>> DMA bindings and replaced them with the standard DMA DT bindings.
>
> The series is rather long, so I may have missed it, but I think you need one
> more patch to the apbdma binding to document the use of #dma-cells, what
> value it has, and what the format of the dma specifiers in slave drivers
> needs to be.
Yes, you're right. I will fold the following into "ARM: tegra: document
use of standard DMA DT bindings":
> diff --git a/Documentation/devicetree/bindings/dma/tegra20-apbdma.txt b/Documentation/devicetree/bindings/dma/tegra20-apbdma.txt
> index 0b1e577ab9d3..0b0f9498e265 100644
> --- a/Documentation/devicetree/bindings/dma/tegra20-apbdma.txt
> +++ b/Documentation/devicetree/bindings/dma/tegra20-apbdma.txt
> @@ -11,6 +11,10 @@ Required properties:
> 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@6000a000 {
> clocks = <&tegra_car 34>;
> resets = <&tegra_car 34>;
> reset-names = "dma";
> + #iommu-cells = <1>;
> };
Follow ups
References