Re: Revert "dmaengine: pl330: add DMA_PAUSE feature"
From: Frank Mori Hess
Date: Fri May 11 2018 - 11:57:19 EST
On Fri, May 11, 2018 at 8:57 AM, Marek Szyprowski
> Okay, so you don't have any evidence that DMA transfers done in single
> reads/writes is broken with the current cmd_pause implementation.
I think the easiest way to test this empirically would be to just hack
dmatest to do a bunch of mem-to-mem transfers which it pauses and
checks the copied data is consistent with the reported residue. Also,
it would need to check the source/destination address registers in the
pl330 for evidence of bytes read but not written. And the pl330.c
driver would need to be fixed to not ignore the requested maxburst
when doing mem-to-mem transfers.