Re: [PATCHv4] DMAEngine: Define interleaved transfer request api

[Williams, Dan J]

On Mon, Oct 3, 2011 at 11:23 AM, Jassi Brar <jaswinder.singh@xxxxxxxxxx> 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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/