lkml.org 
[lkml]   [2011]   [Oct]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCHv4] DMAEngine: Define interleaved transfer request api
From
Date
On Fri, 2011-10-07 at 16:57 +0530, Jassi Brar wrote:
> On 7 October 2011 11:15, Vinod Koul <vinod.koul@intel.com> wrote:
>
> > Thru this patch Jassi gave a very good try at merging DMA_SLAVE and
> > memcpy, but more we debate this, I am still not convinced about merging
> > memcpy and DMA_SLAVE yet.
> >
> Nobody is merging memcpy and DMA_SLAVE right away.
> The api's primary purpose is to support interleave transfers.
> Possibility to merge other prepares into this is a side-effect.
For interleaved isn't that what you are trying?
>
> > I would still argue that if we split this on same lines as current
> > mechanism, we have clean way to convey all details for both cases.
> >
> Do you mean to have separate interleaved transfer apis for Slave
> and Mem->Mem ? Please clarify.
If we can make API cleaner and well defined that way then Yes :)

--
~Vinod



\
 
 \ /
  Last update: 2011-10-07 16:29    [W:0.164 / U:0.392 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site