From: Vinod Koul <vinod.koul@intel.com>
To: Rameshwar Prasad Sahu <rsahu@apm.com>
Cc: dan.j.williams@intel.com, dmaengine@vger.kernel.org,
arnd@arndb.de, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
ddutile@redhat.com, jcm@redhat.com, patches@apm.com,
Loc Ho <lho@apm.com>
Subject: Re: [PATCH v7 3/3] Documentation: dma: Add APM X-Gene SoC DMA engine driver documentation
Date: Mon, 16 Mar 2015 14:59:12 +0530 [thread overview]
Message-ID: <20150316092912.GI32683@intel.com> (raw)
In-Reply-To: <1426158921-8987-4-git-send-email-rsahu@apm.com>
On Thu, Mar 12, 2015 at 04:45:21PM +0530, Rameshwar Prasad Sahu wrote:
> This patch adds device tree binding for APM X-Gene SoC DMA engine driver.
The patch title should be to add the bindings and not Documentation
--
~Vinod
>
> Signed-off-by: Rameshwar Prasad Sahu <rsahu@apm.com>
> Signed-off-by: Loc Ho <lho@apm.com>
> ---
> .../devicetree/bindings/dma/apm-xgene-dma.txt | 47 ++++++++++++++++++++++
> 1 file changed, 47 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/dma/apm-xgene-dma.txt
>
> diff --git a/Documentation/devicetree/bindings/dma/apm-xgene-dma.txt b/Documentation/devicetree/bindings/dma/apm-xgene-dma.txt
> new file mode 100644
> index 0000000..d305876
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/dma/apm-xgene-dma.txt
> @@ -0,0 +1,47 @@
> +Applied Micro X-Gene SoC DMA nodes
> +
> +DMA nodes are defined to describe on-chip DMA interfaces in
> +APM X-Gene SoC.
> +
> +Required properties for DMA interfaces:
> +- compatible: Should be "apm,xgene-dma".
> +- device_type: set to "dma".
> +- reg: Address and length of the register set for the device.
> + It contains the information of registers in the following order:
> + 1st - DMA control and status register address space.
> + 2nd - Descriptor ring control and status register address space.
> + 3rd - Descriptor ring command register address space.
> + 4th - Soc efuse register address space.
> +- interrupts: DMA has 5 interrupts sources. 1st interrupt is
> + DMA error reporting interrupt. 2nd, 3rd, 4th and 5th interrupts
> + are completion interrupts for each DMA channels.
> +- clocks: Reference to the clock entry.
> +
> +Optional properties:
> +- dma-coherent : Present if dma operations are coherent
> +
> +Example:
> + dmaclk: dmaclk@1f27c000 {
> + compatible = "apm,xgene-device-clock";
> + #clock-cells = <1>;
> + clocks = <&socplldiv2 0>;
> + reg = <0x0 0x1f27c000 0x0 0x1000>;
> + reg-names = "csr-reg";
> + clock-output-names = "dmaclk";
> + };
> +
> + dma: dma@1f270000 {
> + compatible = "apm,xgene-storm-dma";
> + device_type = "dma";
> + reg = <0x0 0x1f270000 0x0 0x10000>,
> + <0x0 0x1f200000 0x0 0x10000>,
> + <0x0 0x1b008000 0x0 0x2000>,
> + <0x0 0x1054a000 0x0 0x100>;
> + interrupts = <0x0 0x82 0x4>,
> + <0x0 0xb8 0x4>,
> + <0x0 0xb9 0x4>,
> + <0x0 0xba 0x4>,
> + <0x0 0xbb 0x4>;
> + dma-coherent;
> + clocks = <&dmaclk 0>;
> + };
> --
> 1.8.2.1
>
--
next prev parent reply other threads:[~2015-03-16 9:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 11:15 [PATCH v7 0/3] dmaengine: APM X-Gene SoC DMA engine driver support Rameshwar Prasad Sahu
2015-03-12 11:15 ` [PATCH v7 1/3] dmaengine: Add support for APM X-Gene SoC DMA engine driver Rameshwar Prasad Sahu
2015-03-16 9:27 ` Vinod Koul
2015-03-16 10:30 ` Rameshwar Sahu
2015-03-16 11:27 ` Vinod Koul
2015-03-16 11:54 ` Rameshwar Sahu
2015-03-16 16:26 ` Vinod Koul
2015-03-16 17:31 ` Rameshwar Sahu
2015-03-17 9:33 ` Rameshwar Sahu
2015-03-17 10:19 ` Vinod Koul
2015-03-17 10:38 ` Rameshwar Sahu
2015-03-16 11:02 ` Rameshwar Sahu
2015-03-12 11:15 ` [PATCH v7 2/3] arm64: dts: Add APM X-Gene DMA device and DMA clock DTS nodes Rameshwar Prasad Sahu
2015-03-12 11:15 ` [PATCH v7 3/3] Documentation: dma: Add APM X-Gene SoC DMA engine driver documentation Rameshwar Prasad Sahu
2015-03-16 9:29 ` Vinod Koul [this message]
2015-03-16 10:31 ` Rameshwar Sahu
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=20150316092912.GI32683@intel.com \
--to=vinod.koul@intel.com \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=ddutile@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jcm@redhat.com \
--cc=lho@apm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@apm.com \
--cc=rsahu@apm.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).