public inbox for dmaengine@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Gustavo Pimentel <Gustavo.Pimentel@synopsys.com>
Cc: dmaengine@vger.kernel.org, Joao Pinto <Joao.Pinto@synopsys.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] dmaengine: dw-edma: Fix scatter-gather address calculation
Date: Tue, 25 Aug 2020 16:37:29 +0530	[thread overview]
Message-ID: <20200825110729.GH2639@vkoul-mobl> (raw)
In-Reply-To: <8d3ab7e2ba96563fe3495b32f60077fffb85307d.1597327623.git.gustavo.pimentel@synopsys.com>

On 13-08-20, 16:14, Gustavo Pimentel wrote:
> Fix the source and destination physical address calculation of a
> peripheral device on scatter-gather implementation.
> 
> This issue manifested during tests using a 64 bits architecture system.
> The abnormal behavior wasn't visible before due to all previous tests
> were done using 32 bits architecture system, that masked his effect.

Applied, thanks

> 
> Fixes: e63d79d1ffcd ("dmaengine: Add Synopsys eDMA IP core driver")
> 

Dont leave empty line here

> Cc: Joao Pinto <jpinto@synopsys.com>
> Cc: stable@vger.kernel.org
> Signed-off-by: Gustavo Pimentel <gustavo.pimentel@synopsys.com>
> ---
>  drivers/dma/dw-edma/dw-edma-core.c | 11 ++++++-----
>  1 file changed, 6 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/dma/dw-edma/dw-edma-core.c b/drivers/dma/dw-edma/dw-edma-core.c
> index ed430ad..b971505 100644
> --- a/drivers/dma/dw-edma/dw-edma-core.c
> +++ b/drivers/dma/dw-edma/dw-edma-core.c
> @@ -405,7 +405,7 @@ dw_edma_device_transfer(struct dw_edma_transfer *xfer)
>  			if (xfer->cyclic) {
>  				burst->dar = xfer->xfer.cyclic.paddr;
>  			} else {
> -				burst->dar = sg_dma_address(sg);
> +				burst->dar = dst_addr;
>  				/* Unlike the typical assumption by other
>  				 * drivers/IPs the peripheral memory isn't
>  				 * a FIFO memory, in this case, it's a
> @@ -413,14 +413,13 @@ dw_edma_device_transfer(struct dw_edma_transfer *xfer)
>  				 * and destination addresses are increased
>  				 * by the same portion (data length)
>  				 */
> -				src_addr += sg_dma_len(sg);
>  			}
>  		} else {
>  			burst->dar = dst_addr;
>  			if (xfer->cyclic) {
>  				burst->sar = xfer->xfer.cyclic.paddr;
>  			} else {
> -				burst->sar = sg_dma_address(sg);
> +				burst->sar = src_addr;
>  				/* Unlike the typical assumption by other
>  				 * drivers/IPs the peripheral memory isn't
>  				 * a FIFO memory, in this case, it's a
> @@ -428,12 +427,14 @@ dw_edma_device_transfer(struct dw_edma_transfer *xfer)
>  				 * and destination addresses are increased
>  				 * by the same portion (data length)
>  				 */
> -				dst_addr += sg_dma_len(sg);
>  			}
>  		}
>  
> -		if (!xfer->cyclic)
> +		if (!xfer->cyclic) {
> +			src_addr += sg_dma_len(sg);
> +			dst_addr += sg_dma_len(sg);
>  			sg = sg_next(sg);
> +		}
>  	}
>  
>  	return vchan_tx_prep(&chan->vc, &desc->vd, xfer->flags);
> -- 
> 2.7.4

-- 
~Vinod

      reply	other threads:[~2020-08-25 11:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13 14:14 [PATCH] dmaengine: dw-edma: Fix scatter-gather address calculation Gustavo Pimentel
2020-08-25 11:07 ` Vinod Koul [this message]

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=20200825110729.GH2639@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=Gustavo.Pimentel@synopsys.com \
    --cc=Joao.Pinto@synopsys.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    /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