lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 17 Jun 2013 13:12:32 +0200 From: Arnd Bergmann <arnd@...db.de> To: Joel A Fernandes <joelagnel@...com> Cc: Tony Lindgren <tony@...mide.com>, Sekhar Nori <nsekhar@...com>, Matt Porter <matt@...orter.com>, Grant Likely <grant.likely@...retlab.ca>, Rob Herring <rob.herring@...xeda.com>, Vinod Koul <vinod.koul@...el.com>, Mark Brown <broonie@...nsource.wolfsonmicro.com>, Benoit Cousson <b-cousson@...com>, Russell King <linux@....linux.org.uk>, Rob Landley <rob@...dley.net>, Andrew Morton <akpm@...ux-foundation.org>, Jason Kridner <jkridner@...gleboard.org>, Koen Kooi <koen@...gleboard.org>, Devicetree Discuss <devicetree-discuss@...ts.ozlabs.org>, Linux OMAP List <linux-omap@...r.kernel.org>, Linux ARM Kernel List <linux-arm-kernel@...ts.infradead.org>, Linux DaVinci Kernel List <davinci-linux-open-source@...ux.davincidsp.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Documentation List <linux-doc@...r.kernel.org>, Linux MMC List <linux-mmc@...r.kernel.org>, Linux SPI Devel List <spi-devel-general@...ts.sourceforge.net> Subject: Re: [PATCH v10 5/8] dmaengine: edma: Add TI EDMA device tree binding On Friday 14 June 2013 21:32:47 Joel A Fernandes wrote: > > diff --git a/Documentation/devicetree/bindings/dma/ti-edma.txt b/Documentation/devicetree/bindings/dma/ti-edma.txt > new file mode 100644 > index 0000000..ada0018 > --- /dev/null > +++ b/Documentation/devicetree/bindings/dma/ti-edma.txt > @@ -0,0 +1,26 @@ > +TI EDMA > + > +Required properties: > +- compatible : "ti,edma3" > +- ti,hwmods: Name of the hwmods associated to the EDMA > +- ti,edma-regions: Number of regions > +- ti,edma-slots: Number of slots > + > +Optional properties: > +- ti,edma-xbar-event-map: Crossbar event to channel map You need to list #dma-cells as required here, and which values are accepted by the driver (I suppose only <1>). You should also explain the format of the dma-specifier for a slave here for each possible value of #dma-cells. For each of the standard properties (reg, interrupts, dma-channels), list whether they are optional or required. Since the example has three interrupts, you should probably list how many interrupts need to be specified (minimum and maximum if the number is variable) and in what order to expect them. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists