From: Vinod Koul <vkoul@kernel.org>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: linux-renesas-soc@vger.kernel.org, dmaengine@vger.kernel.org,
geert+renesas@glider.be, niklas.soderlund+renesas@ragnatech.se,
laurent.pinchart+renesas@ideasonboard.com,
Achim.Dahlhoff@de.bosch.com, yoshihiro.shimoda.uh@renesas.com,
ylhuajnu@outlook.com, hiroyuki.yokoyama.vx@renesas.com,
kuninori.morimoto.gx@renesas.com, stable@vger.kernel.org
Subject: [v3,1/2] dmaengine: sh: rcar-dmac: With cyclic DMA residue 0 is valid
Date: Tue, 23 Apr 2019 10:45:54 +0530 [thread overview]
Message-ID: <20190423051554.GF28103@vkoul-mobl> (raw)
On 12-04-19, 07:29, Dirk Behme wrote:
> Having a cyclic DMA, a residue 0 is not an indication of a completed
> DMA. In case of cyclic DMA make sure that dma_set_residue() is called
> and with this a residue of 0 is forwarded correctly to the caller.
Applied both, thanks
WARNING: multiple messages have this Message-ID (diff)
From: Vinod Koul <vkoul@kernel.org>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: linux-renesas-soc@vger.kernel.org, dmaengine@vger.kernel.org,
geert+renesas@glider.be, niklas.soderlund+renesas@ragnatech.se,
laurent.pinchart+renesas@ideasonboard.com,
Achim.Dahlhoff@de.bosch.com, yoshihiro.shimoda.uh@renesas.com,
ylhuajnu@outlook.com, hiroyuki.yokoyama.vx@renesas.com,
kuninori.morimoto.gx@renesas.com, stable@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dmaengine: sh: rcar-dmac: With cyclic DMA residue 0 is valid
Date: Tue, 23 Apr 2019 10:45:54 +0530 [thread overview]
Message-ID: <20190423051554.GF28103@vkoul-mobl> (raw)
Message-ID: <20190423051554.z89bRi4-xaK3b0UdqHHtUUXXeGR57rj0223H7sh5DSM@z> (raw)
In-Reply-To: <20190412052914.16006-1-dirk.behme@de.bosch.com>
On 12-04-19, 07:29, Dirk Behme wrote:
> Having a cyclic DMA, a residue 0 is not an indication of a completed
> DMA. In case of cyclic DMA make sure that dma_set_residue() is called
> and with this a residue of 0 is forwarded correctly to the caller.
Applied both, thanks
--
~Vinod
next prev reply other threads:[~2019-04-23 5:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 5:29 [v3,1/2] dmaengine: sh: rcar-dmac: With cyclic DMA residue 0 is valid Dirk Behme
2019-04-12 5:29 ` [PATCH v3 1/2] " Dirk Behme
2019-04-12 5:29 ` [v3,2/2] dmaengine: sh: rcar-dmac: Fix glitch in dmaengine_tx_status Dirk Behme
2019-04-12 5:29 ` [PATCH v3 2/2] " Dirk Behme
2019-04-12 8:52 ` [v3,2/2] " Yoshihiro Shimoda
2019-04-12 8:52 ` [PATCH v3 2/2] " Yoshihiro Shimoda
2019-04-12 8:33 ` [v3,1/2] dmaengine: sh: rcar-dmac: With cyclic DMA residue 0 is valid Yoshihiro Shimoda
2019-04-12 8:33 ` [PATCH v3 1/2] " Yoshihiro Shimoda
2019-04-12 9:54 ` [v3,1/2] " Laurent Pinchart
2019-04-12 9:54 ` [PATCH v3 1/2] " Laurent Pinchart
2019-04-23 5:15 ` Vinod Koul [this message]
2019-04-23 5:15 ` 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=20190423051554.GF28103@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=Achim.Dahlhoff@de.bosch.com \
--cc=dirk.behme@de.bosch.com \
--cc=dmaengine@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=hiroyuki.yokoyama.vx@renesas.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=stable@vger.kernel.org \
--cc=ylhuajnu@outlook.com \
--cc=yoshihiro.shimoda.uh@renesas.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