From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: vinod.koul@intel.com, linux@arm.linux.org.uk
Cc: tony@atomide.com, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org, dmaengine@vger.kernel.org
Subject: [PATCH 1/4] dmaengine: omap-dma: Correct status reporting for memcpy
Date: Wed, 11 Nov 2015 12:37:55 +0200 [thread overview]
Message-ID: <1447238278-15863-2-git-send-email-peter.ujfalusi@ti.com> (raw)
In-Reply-To: <1447238278-15863-1-git-send-email-peter.ujfalusi@ti.com>
During mem copy both src and dst position moves at the same pace. Check the
dst position for progress reporting.
Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
Tested-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
Signed-off-by: Jyri Sarha <jsarha@ti.com>
---
drivers/dma/omap-dma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/dma/omap-dma.c b/drivers/dma/omap-dma.c
index 1dfc71c90123..8ed39ce24d46 100644
--- a/drivers/dma/omap-dma.c
+++ b/drivers/dma/omap-dma.c
@@ -719,7 +719,7 @@ static enum dma_status omap_dma_tx_status(struct dma_chan *chan,
if (d->dir == DMA_MEM_TO_DEV)
pos = omap_dma_get_src_pos(c);
- else if (d->dir == DMA_DEV_TO_MEM)
+ else if (d->dir == DMA_DEV_TO_MEM || d->dir == DMA_MEM_TO_MEM)
pos = omap_dma_get_dst_pos(c);
else
pos = 0;
--
2.6.2
next prev parent reply other threads:[~2015-11-11 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 10:37 [PATCH 0/4] dmaengine: omap-dma: transfer start and short memcpy improvement Peter Ujfalusi
2015-11-11 10:37 ` Peter Ujfalusi [this message]
2015-11-11 10:37 ` [PATCH 2/4] dmaengine: omap-dma: Clean up the prep_slave_sg sg list walk code Peter Ujfalusi
2015-11-11 10:37 ` [PATCH 3/4] dmaengine: omap-dma: Remove tasklet to start the transfers Peter Ujfalusi
2015-11-11 10:37 ` [PATCH 4/4] dmaengine: omap-dma: Handle cases when the channel is polled for completion Peter Ujfalusi
2015-12-05 8:07 ` [PATCH 0/4] dmaengine: omap-dma: transfer start and short memcpy improvement Vinod Koul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1447238278-15863-2-git-send-email-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=tony@atomide.com \
--cc=vinod.koul@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox