ac100 team mailing list archive
-
ac100 team
-
Mailing list archive
-
Message #01186
Re: [PATCH 00/31] ARM: tegra: use common reset and DMA bindings
-
To:
Stephen Warren <swarren@xxxxxxxxxxxxx>
-
From:
Martino Brandolini <martinobrandolini@xxxxxxxxx>
-
Date:
Wed, 20 Nov 2013 20:17:33 +0100
-
Cc:
Mark Rutland <mark.rutland@xxxxxxx>, alsa-devel@xxxxxxxxxxxxxxxx, linux-usb@xxxxxxxxxxxxxxx, Wolfram Sang <wsa@xxxxxxxxxxxxx>, David Airlie <airlied@xxxxxxxx>, linux-pci@xxxxxxxxxxxxxxx, dri-devel@xxxxxxxxxxxxxxxxxxxxx, linux-tegra@xxxxxxxxxxxxxxx, linux-i2c@xxxxxxxxxxxxxxx, ac100@xxxxxxxxxxxxxxxxxxx, devel@xxxxxxxxxxxxxxxxxxxx, Stephen Warren <swarren@xxxxxxxxxx>, Arnd Bergmann <arnd@xxxxxxxx>, Terje Bergström <tbergstrom@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>, Bjorn Helgaas <bhelgaas@xxxxxxxxxx>, Mike Turquette <mturquette@xxxxxxxxxx>, Dan Williams <dan.j.williams@xxxxxxxxx>, linux-arm-kernel@xxxxxxxxxxxxxxxxxxx, Dmitry Torokhov <dtor@xxxxxxx>, pdeschrijver@xxxxxxxxxx, Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>, Liam Girdwood <lgirdwood@xxxxxxxxx>, linux-spi@xxxxxxxxxxxxxxx, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
-
In-reply-to:
<528CE71D.5090300@wwwdotorg.org>
Dear all,
My ac100 screen is flickering so much. I realized I'm not using it anymore.
So if anyone wants to have it for free would be for me a huge pleasure to
give it away. I'm based in milan and I'll be in London for the next week.
Maybe someone needs it.
Martino
2013/11/20 Stephen Warren <swarren@xxxxxxxxxxxxx>
> 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>;
> > };
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~ac100
> Post to : ac100@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ac100
> More help : https://help.launchpad.net/ListHelp
>
References
