From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: <vinod.koul@intel.com>, <linux@arm.linux.org.uk>,
<tony@atomide.com>, <dmaengine@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-omap@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<dan.j.williams@intel.com>
Subject: Re: [PATCH] dmaengine: omap-dma: Add support for memcpy
Date: Tue, 8 Sep 2015 15:25:33 +0300 [thread overview]
Message-ID: <55EED3BD.1080605@ti.com> (raw)
In-Reply-To: <3187470.tKXzQaPa1m@avalon>
Laurent,
On 09/08/2015 02:24 PM, Laurent Pinchart wrote:
> Hi Peter,
>
> Thank you for the patch.
>
> While trying to port the omap_vout driver to the DMA engine API I noticed that
> the driver makes use of double-indexed transfers, which are not supported by
> the omap-dma driver. I haven't checked in details what would be required, but
> the interleaved API might be a good candidate for this. Do you have any plan
> to add support for double-indexed transfers to the omap-dma driver ?
If double-indexed transfer support is needed by drivers still using the
legacy/direct sDMA API, then I don't think we have other options..
So far I have not looked at that part and where it would fit.
I'll try to find time to look at this. I hope not in the distant future ;)
> On Wednesday 22 April 2015 10:34:29 Peter Ujfalusi wrote:
>> The sDMA controller is capable of performing memory copy operation. It need
>> to be configured to software triggered mode and without HW synchronization.
>> The sDMA can copy data which is aligned to 8, 16 or 32 bits.
>>
>> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
>> ---
>> drivers/dma/omap-dma.c | 51 +++++++++++++++++++++++++++++++++++++++++++++--
>> 1 file changed, 49 insertions(+), 2 deletions(-)
>
--
Péter
prev parent reply other threads:[~2015-09-08 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 7:34 [PATCH] dmaengine: omap-dma: Add support for memcpy Peter Ujfalusi
2015-05-04 8:35 ` Vinod Koul
2015-09-08 11:24 ` Laurent Pinchart
2015-09-08 12:25 ` Peter Ujfalusi [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=55EED3BD.1080605@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--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=tony@atomide.com \
--cc=vinod.koul@intel.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