Re: [PATCH 6/9] crypto: ux500/cryp - Set DMA configuration though dma_slave_config()

From: Arnd Bergmann
Date: Fri Apr 26 2013 - 05:39:22 EST

On Friday 26 April 2013 13:46:46 Vinod Koul wrote:
> The mapping & unmapping of dma buffer (memcpy and memory buffer in this txn) is
> required to be performed by the client driver. The dmanegine or dmaengine driver
> will not do that for you...

I've been wondering about this part: since we need to pass the 'struct device' of
the dma engine (rather than the slave) into dma_map_single, what is the official
way to do that? Should the slave driver just rely on dma_chan->device->dev to
work correctly for the purpose of dma-mapping.h interfaces?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at