diff options
author | Vinod Koul <vinod.koul@intel.com> | 2013-10-16 11:59:02 +0400 |
---|---|---|
committer | Vinod Koul <vinod.koul@intel.com> | 2013-10-25 09:45:38 +0400 |
commit | adfedd9a32e4e3490c0060576fd824881572b72a (patch) | |
tree | 83c422afd052ce038ed32d766e11ddbc690a0209 /drivers/dma | |
parent | e98b3cafe5f048be40ff6acb18dfa7c9a0e9423e (diff) | |
download | linux-adfedd9a32e4e3490c0060576fd824881572b72a.tar.xz |
dmaengine: use DMA_COMPLETE for dma completion status
the DMA_SUCCESS is a misnomer as dmaengine indicates the transfer is complete and
gives no guarantee of the transfer success. Hence we should use DMA_COMPLTE
instead of DMA_SUCCESS
Acked-by: Dan Williams <dan.j.williams@intel.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Diffstat (limited to 'drivers/dma')
-rw-r--r-- | drivers/dma/dmaengine.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/dma/dmaengine.c b/drivers/dma/dmaengine.c index 9162ac80c18f..81d876528c70 100644 --- a/drivers/dma/dmaengine.c +++ b/drivers/dma/dmaengine.c @@ -1062,7 +1062,7 @@ dma_wait_for_async_tx(struct dma_async_tx_descriptor *tx) unsigned long dma_sync_wait_timeout = jiffies + msecs_to_jiffies(5000); if (!tx) - return DMA_SUCCESS; + return DMA_COMPLETE; while (tx->cookie == -EBUSY) { if (time_after_eq(jiffies, dma_sync_wait_timeout)) { |