Laurent, On 09/08/2015 02:24 PM, Laurent Pinchart wrote: > Hi Peter, > > Thank you for the patch. > > While trying to port the omap_vout driver to the DMA engine API I noticed that > the driver makes use of double-indexed transfers, which are not supported by > the omap-dma driver. I haven't checked in details what would be required, but > the interleaved API might be a good candidate for this. Do you have any plan > to add support for double-indexed transfers to the omap-dma driver ? If double-indexed transfer support is needed by drivers still using the legacy/direct sDMA API, then I don't think we have other options.. So far I have not looked at that part and where it would fit. I'll try to find time to look at this. I hope not in the distant future ;) > On Wednesday 22 April 2015 10:34:29 Peter Ujfalusi wrote: >> 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 <peter.ujfalusi@xxxxxx> >> --- >> drivers/dma/omap-dma.c | 51 +++++++++++++++++++++++++++++++++++++++++++++-- >> 1 file changed, 49 insertions(+), 2 deletions(-) > -- Péter -- To unsubscribe from this list: send the line "unsubscribe dmaengine" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
