From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/7] dmaengine: xilinx_vdma: Add Support for Xilinx AXI Direct Memory Access Engine
Date: Wed, 16 Mar 2016 08:47:21 +0530 [thread overview]
Message-ID: <20160316031721.GO13211@localhost> (raw)
In-Reply-To: <1458062592-27981-5-git-send-email-appanad@xilinx.com>
On Tue, Mar 15, 2016 at 10:53:09PM +0530, Kedareswara rao Appana wrote:
> This patch updates the device-tree binding doc for
> adding support for AXI DMA.
Binding patch should precced the driver. and the title doesn't tell me its a
binding patch and might get ignore by folks.
Pls cc device tree ML on these patches. And please read
Documentation/devicetree/bindings/submitting-patches.txt. Its there for a
purpose
>
> Signed-off-by: Kedareswara rao Appana <appanad@xilinx.com>
> ---
> .../devicetree/bindings/dma/xilinx/xilinx_vdma.txt | 22 +++++++++++++++++++++-
> 1 file changed, 21 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt b/Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt
> index e4c4d47..3d134a5 100644
> --- a/Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt
> +++ b/Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt
> @@ -3,8 +3,13 @@ It can be configured to have one channel or two channels. If configured
> as two channels, one is to transmit to the video device and another is
> to receive from the video device.
>
> +Xilinx AXI DMA engine, it does transfers between memory and AXI4 stream
> +target devices. It can be configured to have one channel or two channels.
> +If configured as two channels, one is to transmit to the device and another
> +is to receive from the device.
> +
> Required properties:
> -- compatible: Should be "xlnx,axi-vdma-1.00.a"
> +- compatible: Should be "xlnx,axi-vdma-1.00.a" or "xlnx,axi-dma-1.00.a"
> - #dma-cells: Should be <1>, see "dmas" property below
> - reg: Should contain VDMA registers location and length.
> - xlnx,num-fstores: Should be the number of framebuffers as configured in h/w.
> @@ -55,6 +60,21 @@ axi_vdma_0: axivdma at 40030000 {
> } ;
> } ;
>
> +axi_dma_0: axidma at 40400000 {
> + compatible = "xlnx,axi-dma-1.00.a";
> + #dma_cells = <1>;
> + reg = < 0x40400000 0x10000 >;
> + dma-channel at 40400000 {
> + compatible = "xlnx,axi-vdma-mm2s-channel";
> + interrupts = < 0 59 4 >;
> + xlnx,datawidth = <0x40>;
> + } ;
> + dma-channel at 40400030 {
> + compatible = "xlnx,axi-vdma-s2mm-channel";
> + interrupts = < 0 58 4 >;
> + xlnx,datawidth = <0x40>;
> + } ;
> +} ;
>
> * DMA client
>
> --
> 2.1.2
>
--
~Vinod
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vinod.koul@intel.com>
To: Kedareswara rao Appana <appana.durga.rao@xilinx.com>
Cc: dan.j.williams@intel.com, michal.simek@xilinx.com,
soren.brinkmann@xilinx.com, appanad@xilinx.com,
moritz.fischer@ettus.com, laurent.pinchart@ideasonboard.com,
luis@debethencourt.com, anirudh@xilinx.com,
dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/7] dmaengine: xilinx_vdma: Add Support for Xilinx AXI Direct Memory Access Engine
Date: Wed, 16 Mar 2016 08:47:21 +0530 [thread overview]
Message-ID: <20160316031721.GO13211@localhost> (raw)
In-Reply-To: <1458062592-27981-5-git-send-email-appanad@xilinx.com>
On Tue, Mar 15, 2016 at 10:53:09PM +0530, Kedareswara rao Appana wrote:
> This patch updates the device-tree binding doc for
> adding support for AXI DMA.
Binding patch should precced the driver. and the title doesn't tell me its a
binding patch and might get ignore by folks.
Pls cc device tree ML on these patches. And please read
Documentation/devicetree/bindings/submitting-patches.txt. Its there for a
purpose
>
> Signed-off-by: Kedareswara rao Appana <appanad@xilinx.com>
> ---
> .../devicetree/bindings/dma/xilinx/xilinx_vdma.txt | 22 +++++++++++++++++++++-
> 1 file changed, 21 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt b/Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt
> index e4c4d47..3d134a5 100644
> --- a/Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt
> +++ b/Documentation/devicetree/bindings/dma/xilinx/xilinx_vdma.txt
> @@ -3,8 +3,13 @@ It can be configured to have one channel or two channels. If configured
> as two channels, one is to transmit to the video device and another is
> to receive from the video device.
>
> +Xilinx AXI DMA engine, it does transfers between memory and AXI4 stream
> +target devices. It can be configured to have one channel or two channels.
> +If configured as two channels, one is to transmit to the device and another
> +is to receive from the device.
> +
> Required properties:
> -- compatible: Should be "xlnx,axi-vdma-1.00.a"
> +- compatible: Should be "xlnx,axi-vdma-1.00.a" or "xlnx,axi-dma-1.00.a"
> - #dma-cells: Should be <1>, see "dmas" property below
> - reg: Should contain VDMA registers location and length.
> - xlnx,num-fstores: Should be the number of framebuffers as configured in h/w.
> @@ -55,6 +60,21 @@ axi_vdma_0: axivdma@40030000 {
> } ;
> } ;
>
> +axi_dma_0: axidma@40400000 {
> + compatible = "xlnx,axi-dma-1.00.a";
> + #dma_cells = <1>;
> + reg = < 0x40400000 0x10000 >;
> + dma-channel@40400000 {
> + compatible = "xlnx,axi-vdma-mm2s-channel";
> + interrupts = < 0 59 4 >;
> + xlnx,datawidth = <0x40>;
> + } ;
> + dma-channel@40400030 {
> + compatible = "xlnx,axi-vdma-s2mm-channel";
> + interrupts = < 0 58 4 >;
> + xlnx,datawidth = <0x40>;
> + } ;
> +} ;
>
> * DMA client
>
> --
> 2.1.2
>
--
~Vinod
next prev parent reply other threads:[~2016-03-16 3:17 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 17:23 [PATCH 0/7] dmaengine: xilinx_vdma: AXI DMA's enhancments Kedareswara rao Appana
2016-03-15 17:23 ` Kedareswara rao Appana
2016-03-15 17:23 ` [PATCH 1/7] dmaengine: xilinx_vdma: Fix checkpatch.pl warnings Kedareswara rao Appana
2016-03-15 17:23 ` Kedareswara rao Appana
2016-03-15 17:50 ` Moritz Fischer
2016-03-15 17:50 ` Moritz Fischer
2016-03-17 7:00 ` Laurent Pinchart
2016-03-17 7:00 ` Laurent Pinchart
2016-03-15 17:23 ` [PATCH 2/7] dmaengine: xilinx_vdma: Add quirks support to differentiate differnet IP cores Kedareswara rao Appana
2016-03-15 17:23 ` Kedareswara rao Appana
2016-03-16 3:13 ` Vinod Koul
2016-03-16 3:13 ` Vinod Koul
2016-03-16 6:12 ` Appana Durga Kedareswara Rao
2016-03-16 6:12 ` Appana Durga Kedareswara Rao
2016-03-17 7:19 ` Laurent Pinchart
2016-03-17 7:19 ` Laurent Pinchart
2016-03-18 12:43 ` Appana Durga Kedareswara Rao
2016-03-18 12:43 ` Appana Durga Kedareswara Rao
2016-03-15 17:23 ` [PATCH 3/7] dmaengine: xilinx_vdma: Add Support for Xilinx AXI Direct Memory Access Engine Kedareswara rao Appana
2016-03-15 17:23 ` Kedareswara rao Appana
2016-03-17 8:05 ` Laurent Pinchart
2016-03-17 8:05 ` Laurent Pinchart
2016-03-18 12:43 ` Appana Durga Kedareswara Rao
2016-03-18 12:43 ` Appana Durga Kedareswara Rao
2016-03-15 17:23 ` [PATCH 4/7] " Kedareswara rao Appana
2016-03-15 17:23 ` Kedareswara rao Appana
2016-03-16 3:17 ` Vinod Koul [this message]
2016-03-16 3:17 ` Vinod Koul
2016-03-16 6:19 ` Appana Durga Kedareswara Rao
2016-03-16 6:19 ` Appana Durga Kedareswara Rao
2016-03-15 17:23 ` [PATCH 5/7] dmaengine: xilinx_vdma: Remove unnecessary axi dma device-tree binding doc Kedareswara rao Appana
2016-03-15 17:23 ` Kedareswara rao Appana
2016-03-16 1:34 ` Moritz Fischer
2016-03-16 1:34 ` Moritz Fischer
2016-03-16 6:08 ` Appana Durga Kedareswara Rao
2016-03-16 6:08 ` Appana Durga Kedareswara Rao
2016-03-15 17:23 ` [PATCH 6/7] dmaengine: xilinx_vdma: Add Support for Xilinx AXI Central Direct Memory Access Engine Kedareswara rao Appana
2016-03-15 17:23 ` Kedareswara rao Appana
2016-03-15 17:23 ` [PATCH 7/7] " Kedareswara rao Appana
2016-03-15 17:23 ` Kedareswara rao Appana
2016-03-16 1:29 ` [PATCH 0/7] dmaengine: xilinx_vdma: AXI DMA's enhancments Moritz Fischer
2016-03-16 1:29 ` Moritz Fischer
2016-03-16 3:11 ` Vinod Koul
2016-03-16 3:11 ` Vinod Koul
2016-03-16 6:13 ` Appana Durga Kedareswara Rao
2016-03-16 6:13 ` Appana Durga Kedareswara Rao
2016-03-16 6:06 ` Appana Durga Kedareswara Rao
2016-03-16 6:06 ` Appana Durga Kedareswara Rao
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=20160316031721.GO13211@localhost \
--to=vinod.koul@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.