From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4] dma: Add Xilinx AXI Direct Memory Access Engine driver support
Date: Wed, 15 Oct 2014 16:00:36 +0100 [thread overview]
Message-ID: <20141015150036.GF20034@leverpostej> (raw)
In-Reply-To: <20141015133248.GQ1638@intel.com>
On Wed, Oct 15, 2014 at 02:32:48PM +0100, Vinod Koul wrote:
> On Wed, Oct 15, 2014 at 01:45:28PM +0100, Mark Rutland wrote:
> > Hi,
> >
> > On Wed, Oct 15, 2014 at 01:00:36PM +0100, Srikanth Thokala wrote:
> > > This is the driver for the AXI Direct Memory Access (AXI DMA)
> > > core, which is a soft Xilinx IP core that provides high-
> > > bandwidth direct memory access between memory and AXI4-Stream
> > > type target peripherals.
> > >
> > > This module works on Zynq (ARM Based SoC) and Microblaze platforms.
> > >
> > > Signed-off-by: Srikanth Thokala <sthokal@xilinx.com>
> > > ---
> > > Changes in v4:
> > > - Add direction field to VDMA descriptor structure and removed from
> > > channel structure to avoid duplication.
> > > - Check for DMA idle condition before changing the configuration.
> > > - Residue is being calculated in complete_descriptor() and is reported
> > > to slave driver.
> > >
> > > Changes in v3:
> > > - Rebased on 3.16-rc7
> > >
> > > Changes in v2:
> > > - Simplified the logic to set SOP and APP words in prep_slave_sg().
> > > - Corrected function description comments to match the return type.
> > > - Fixed some minor comments as suggested by Andy, Thanks.
> >
> > This patch has come without the necessary device tree binding document,
> > and I was not able to find an existing binding document upstream (I
> > searched for "xlnx,axi-dma-1.00.a" and "axi-dma").
> which tree did you grep.
Torvalds'
> This is present in slave-dmaengine.git
>
> commit ddc643630f5deb1995d191719086b64873c67a44
> Author: Srikanth Thokala <sthokal@xilinx.com>
> Date: Mon Jul 28 17:47:48 2014 +0530
>
> dma: Add Xilinx AXI DMA DT Binding Documentation
>
> Device-tree binding documentation of Xilinx DMA Engine
>
> Signed-off-by: Srikanth Thokala <sthokal@xilinx.com>
> Acked-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
I see. Thanks for the pointer.
Mark.
next prev parent reply other threads:[~2014-10-15 15:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 12:00 [PATCH v4] dma: Add Xilinx AXI Direct Memory Access Engine driver support Srikanth Thokala
2014-10-15 12:45 ` Mark Rutland
2014-10-15 13:32 ` Vinod Koul
2014-10-15 15:00 ` Mark Rutland [this message]
2014-10-15 14:34 ` Srikanth Thokala
2014-10-20 19:37 ` Arnd Bergmann
2014-10-21 9:06 ` Appana Durga Kedareswara Rao
2014-10-21 9:14 ` Arnd Bergmann
2014-10-24 12:08 ` Appana Durga Kedareswara Rao
2014-10-24 13:58 ` Arnd Bergmann
2015-01-19 14:08 ` Appana Durga Kedareswara Rao
2015-01-29 11:24 ` Appana Durga Kedareswara Rao
2015-02-12 9:34 ` Vinod Koul
2015-02-14 14:21 ` Appana Durga Kedareswara Rao
2015-02-20 6:29 ` Vinod Koul
2015-02-20 10:42 ` Michal Simek
2015-03-02 16:38 ` Vinod Koul
[not found] ` <54E70F97.30908@xilinx.com>
2015-03-02 9:04 ` Appana Durga Kedareswara Rao
2015-02-05 13:31 ` 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=20141015150036.GF20034@leverpostej \
--to=mark.rutland@arm.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 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).