[COMMON] dma: Remove FLUSHP for dev2mem transfer

In Dev2mem transfer, peripheral de-asserts the PERIPHERAL_REQUEST
on the very next clock edge of its finished request because
data transfer is already completed on the peripheral side.

In this case, micro code does not have to do FLUSHP
because there should not be any synchronization issues.

Change-Id: I7370b526759422b1d056f0c54c65899597e327a4
Signed-off-by: Eunok Jo <eunok25.jo@samsung.com>

diff --git a/drivers/dma/pl330.c b/drivers/dma/pl330.c
index e458f7d8f589241615428d58e4de7622d8555511..033a263f95abe99f03c997c44c2e757b4dbfc2c2 100644 (file)
--- a/drivers/dma/pl330.c
+++ b/drivers/dma/pl330.c
@@ -1137,10 +1137,6 @@ static inline int _ldst_devtomem(struct pl330_dmac *pl330, unsigned dry_run,
                off += _emit_WFP(dry_run, &buf[off], cond, pxs->desc->peri);
                off += _emit_LDP(dry_run, &buf[off], cond, pxs->desc->peri);
                off += _emit_ST(dry_run, &buf[off], ALWAYS);
-
-               if (!(pl330->quirks & PL330_QUIRK_BROKEN_NO_FLUSHP))
-                       off += _emit_FLUSHP(dry_run, &buf[off],
-                                           pxs->desc->peri);
        }
 
        return off;