lkml.org 
[lkml]   [2011]   [Oct]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCHv4] DMAEngine: Define interleaved transfer request api
From
On Mon, Oct 3, 2011 at 11:23 AM, Jassi Brar <jaswinder.singh@linaro.org> wrote:
> You are assuming only Slave usage.
> src_inc/dst_inc are mainly for 'Memset' type operation.

There currently are not any users of offloaded memset in the kernel,
do you have one in mind? Otherwise I would not design for it this
early.

> In Slave transfer they would help avoid allocating full length RX buffer
> when the client only wants to send data but the controller works
> only in full-duplex and vice-versa (thanks to RMK for pointing the case,
> and I remember S3C24XX do have such SPI controller).
> More generally when one needs to transmit the same data, or discard
> the received data, for a certain period of time.

In the slave case I would think the driver would know the address
increment attributes of the slave and would not need to be told on
each operation by the client?


\
 
 \ /
  Last update: 2011-10-05 20:21    [W:0.254 / U:0.712 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site