kernel.git/drivers/dma/omap-dma.c, branch linux-4.2.y

Merge branch 'topic/omap' into for-linus

2015-06-25T03:51:43Z

dmaengine: omap-dma: Reduce the number of virtual channels

2015-05-09T11:41:26Z

Since the mapping between the hardware request lines and channels has been removed it no longer make sense to have too many channels. Set the number of channels to match with the number of logical channels supported by sDMA. Signed-off-by: Peter Ujfalusi Signed-off-by: Vinod Koul

dmaengine: omap-dma: Remove mapping between virtual channels and requests

2015-05-09T11:41:25Z

Do not direct map the virtual channels to sDMA request number. When the sDMA is behind of a crossbar this direct mapping can cause situations when certain channel can not be requested since the crossbar request number will no longer match with the sDMA request line. The direct mapping for virtual channels with HW request lines will make it harder to implement MEM_TO_MEM mode for the driver. Signed-off-by: Peter Ujfalusi Signed-off-by: Vinod Koul

dmaengine: omap-dma: Take DMA request number from DT if it is available

2015-05-09T11:41:25Z

Use the dma-requests property from DT to get the number of DMA requests. In case of legacy boot or failure to find the property, use the default 127 as number of requests. Signed-off-by: Peter Ujfalusi Signed-off-by: Vinod Koul

dmaengine: omap-dma: Use defines for dma channels and request count

2015-05-09T11:41:25Z

Instead of magic numbers in the code, use define for number of logical DMA channels and DMA requests. Signed-off-by: Peter Ujfalusi Signed-off-by: Vinod Koul

dmaengine: omap-dma: Add support for memcpy

2015-05-04T08:35:10Z

The sDMA controller is capable of performing memory copy operation. It need to be configured to software triggered mode and without HW synchronization. The sDMA can copy data which is aligned to 8, 16 or 32 bits. Signed-off-by: Peter Ujfalusi Signed-off-by: Vinod Koul

dmaengine: omap-dma: Fix memory leak when terminating running transfer

2015-03-30T17:47:08Z

In omap_dma_start_desc the vdesc->node is removed from the virt-dma framework managed lists (to be precise from the desc_issued list). If a terminate_all comes before the transfer finishes the omap_desc will not be freed up because it is not in any of the lists and we stopped the DMA channel so the transfer will not going to complete. There is no special sequence for leaking memory when using cyclic (audio) transfer: with every start and stop of a cyclic transfer the driver leaks struct omap_desc worth of memory. Free up the allocated memory directly in omap_dma_terminate_all() since the framework will not going to do that for us. Signed-off-by: Peter Ujfalusi CC: CC: Signed-off-by: Vinod Koul

dmaengine: omap: fix the assignment to .device_config

2014-12-22T07:04:22Z

Signed-off-by: Vinod Koul

dmaengine: omap: Declare slave capabilities for the generic code

2014-12-22T07:03:24Z

Now that the generic slave caps code can make use of the device assigned capabilities, instead of relying on a callback to be implemented. Make use of this code. Signed-off-by: Maxime Ripard Signed-off-by: Vinod Koul

dmaengine: omap: Split device_control

2014-12-22T06:59:07Z

Split the device_control callback of the TI OMAP DMA driver to make use of the newly introduced callbacks, that will eventually be used to retrieve slave capabilities. Signed-off-by: Maxime Ripard Signed-off-by: Vinod Koul