From: Vinod Koul <vinod.koul@intel.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
tony@atomide.com, linux@arm.linux.org.uk
Subject: Re: [PATCH] dmaengine: omap-dma: Support for interleaved transfer
Date: Sun, 24 Jul 2016 11:15:09 +0530 [thread overview]
Message-ID: <20160724054509.GS9681@localhost> (raw)
In-Reply-To: <20160712112114.8478-1-peter.ujfalusi@ti.com>
On Tue, Jul 12, 2016 at 02:21:14PM +0300, Peter Ujfalusi wrote:
> Initial support for interleaved transfer with sDMA.
> The implementation only supports DMA_MEM_TO_MEM and frame_size must be 1.
> sDMA needs to be configured for double indexing when ICG is needed.
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2016-07-24 5:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 11:21 [PATCH] dmaengine: omap-dma: Support for interleaved transfer Peter Ujfalusi
2016-07-24 5:45 ` Vinod Koul [this message]
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=20160724054509.GS9681@localhost \
--to=vinod.koul@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=peter.ujfalusi@ti.com \
--cc=tony@atomide.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).