From: Frank Li <Frank.li@oss.nxp.com>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: "Viresh Kumar" <vireshk@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Vinod Koul" <vkoul@kernel.org>, "Frank Li" <Frank.Li@kernel.org>,
"Dan Williams" <djbw@kernel.org>,
"Serge Semin" <fancer.lancer@gmail.com>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
dmaengine@vger.kernel.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, Sashiko <sashiko-bot@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>
Subject: Re: [PATCH v6 04/10] dmaengine: dw: extract hardware-LLP residue calculation
Date: Wed, 4 Nov 2026 14:07:54 -0600 [thread overview]
Message-ID: <auuQmvQq2k_LH6Dy@SMW015318> (raw)
In-Reply-To: <20261103-submit-dw-dma-synchronize-v1-v6-4-2ee0c348224d@gmail.com>
On Tue, Nov 03, 2026 at 03:26:06PM -0700, James Hilliard wrote:
> From: Serge Semin <fancer.lancer@gmail.com>
>
> Move the hardware-LLP residue calculation into
> dwc_get_hard_llp_desc_residue() so it can be reused independently of
> completion handling.
>
> Keep the scanner's LLP snapshot, descriptor updates and early returns
> unchanged. The helper reports whether it found the current descriptor,
> including when that descriptor has zero residue, rather than using the
> residue value as a completion indication.
>
> Signed-off-by: Serge Semin <fancer.lancer@gmail.com>
> [james: extract the calculation without changing scanner behavior]
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> drivers/dma/dw/core.c | 58 +++++++++++++++++++++++++++++----------------------
> 1 file changed, 33 insertions(+), 25 deletions(-)
>
> diff --git a/drivers/dma/dw/core.c b/drivers/dma/dw/core.c
> index 2d69fab06601..5a1caca7ad68 100644
> --- a/drivers/dma/dw/core.c
> +++ b/drivers/dma/dw/core.c
> @@ -267,6 +267,38 @@ static inline u32 dwc_get_sent(struct dw_dma_chan *dwc)
> return dw->block2bytes(dwc, ctlhi, ctllo >> 4 & 7);
> }
>
> +static bool dwc_get_hard_llp_desc_residue(struct dw_dma_chan *dwc,
> + struct dw_desc *desc, dma_addr_t llp)
> +{
> + struct dw_desc *child;
> +
> + /* Initial residue value */
> + desc->residue = desc->total_len;
> +
> + /* Check first descriptors addr */
> + if (desc->txd.phys == DWC_LLP_LOC(llp))
> + return true;
> +
> + /* Check first descriptors llp */
> + if (lli_read(desc, llp) == llp) {
> + /* This one is currently in progress */
> + desc->residue -= dwc_get_sent(dwc);
> + return true;
> + }
> +
> + desc->residue -= desc->len;
> + list_for_each_entry(child, &desc->tx_list, desc_node) {
> + if (lli_read(child, llp) == llp) {
> + /* Currently in progress */
> + desc->residue -= dwc_get_sent(dwc);
> + return true;
> + }
> + desc->residue -= child->len;
> + }
> +
> + return false;
> +}
> +
> static void dwc_scan_descriptors(struct dw_dma *dw, struct dw_dma_chan *dwc)
> {
> dma_addr_t llp;
> @@ -354,34 +386,10 @@ static void dwc_scan_descriptors(struct dw_dma *dw, struct dw_dma_chan *dwc)
> dev_vdbg(dmaengine_chan_dev(&dwc->chan), "%s: llp=%pad\n", __func__, &llp);
>
> list_for_each_entry_safe(desc, _desc, &dwc->active_list, desc_node) {
> - /* Initial residue value */
> - desc->residue = desc->total_len;
> -
> - /* Check first descriptors addr */
> - if (desc->txd.phys == DWC_LLP_LOC(llp)) {
> - spin_unlock_irqrestore(&dwc->lock, flags);
> - return;
> - }
> -
> - /* Check first descriptors llp */
> - if (lli_read(desc, llp) == llp) {
> - /* This one is currently in progress */
> - desc->residue -= dwc_get_sent(dwc);
> + if (dwc_get_hard_llp_desc_residue(dwc, desc, llp)) {
> spin_unlock_irqrestore(&dwc->lock, flags);
> return;
> }
> -
> - desc->residue -= desc->len;
> - list_for_each_entry(child, &desc->tx_list, desc_node) {
> - if (lli_read(child, llp) == llp) {
> - /* Currently in progress */
> - desc->residue -= dwc_get_sent(dwc);
> - spin_unlock_irqrestore(&dwc->lock, flags);
> - return;
> - }
> - desc->residue -= child->len;
> - }
> -
> }
>
> /* Residue describes source reads; only RAW.XFER completes a transfer. */
>
> --
> 2.53.0
>
next prev parent reply other threads:[~2026-11-04 20:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 22:26 [PATCH v6 00/10] dmaengine: dw: serialize completion and termination James Hilliard
2026-11-03 22:26 ` [PATCH v6 01/10] dmaengine: dw: Fix XFER bit set, but channel not idle error James Hilliard
2026-11-03 22:26 ` [PATCH v6 02/10] dmaengine: dw: serialize error recovery with channel termination James Hilliard
2026-11-03 22:26 ` [PATCH v6 03/10] dmaengine: dw: complete cookies before releasing the channel lock James Hilliard
2026-11-03 22:26 ` [PATCH v6 04/10] dmaengine: dw: extract hardware-LLP residue calculation James Hilliard
2026-11-04 20:07 ` Frank Li [this message]
2026-11-03 22:26 ` [PATCH v6 05/10] dmaengine: dw: calculate residue in the status getter James Hilliard
2026-11-04 20:21 ` Frank Li
2026-11-03 22:26 ` [PATCH v6 06/10] dmaengine: dw: simplify transfer-complete handling James Hilliard
2026-11-04 20:27 ` Frank Li
2026-11-03 22:26 ` [PATCH v6 07/10] dmaengine: dw: report residue for queued transfers James Hilliard
2026-11-03 22:26 ` [PATCH v6 08/10] dmaengine: dw: drain the tasklet before releasing channel resources James Hilliard
2026-11-03 22:26 ` [PATCH v6 09/10] dmaengine: dw: synchronize completion callbacks James Hilliard
2026-11-03 22:26 ` [PATCH v6 10/10] dmaengine: dw: Prevent tx-status calling DMA-desc callback James Hilliard
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=auuQmvQq2k_LH6Dy@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=djbw@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=james.hilliard1@gmail.com \
--cc=jirislaby@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=vireshk@kernel.org \
--cc=vkoul@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
all inboxes | Powered by JetHome®