Re: [PATCH v4 1/3] dmaengine: add dma_get_slave_sg_limits()

2013-05-29 Thread Lars-Peter Clausen
On 03/06/2013 08:56 PM, Matt Porter wrote: > Add a dmaengine API to retrieve slave SG transfer limits. > > The API is optionally implemented by dmaengine drivers and when > unimplemented will return a NULL pointer. A client driver using > this API provides the required dma channel, address width,

Re: [PATCH v4 1/3] dmaengine: add dma_get_slave_sg_limits()

2013-03-21 Thread Vinod Koul
On Wed, Mar 06, 2013 at 02:56:05PM -0500, Matt Porter wrote: > Add a dmaengine API to retrieve slave SG transfer limits. > > The API is optionally implemented by dmaengine drivers and when > unimplemented will return a NULL pointer. A client driver using > this API provides the required dma channe

Re: [PATCH v4 1/3] dmaengine: add dma_get_slave_sg_limits()

2013-03-11 Thread Lars-Peter Clausen
[...] > * struct with auxiliary transfer status information, otherwise the call > * will just return a simple status code > * @device_issue_pending: push pending transactions to hardware > + * @device_slave_sg_limits: return the slave SG capabilities > */ > struct dma_device { > > @@

[PATCH v4 1/3] dmaengine: add dma_get_slave_sg_limits()

2013-03-06 Thread Matt Porter
Add a dmaengine API to retrieve slave SG transfer limits. The API is optionally implemented by dmaengine drivers and when unimplemented will return a NULL pointer. A client driver using this API provides the required dma channel, address width, and burst size of the transfer. dma_get_slave_sg_limi