DMA Engine development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "James Hilliard" <james.hilliard1@gmail.com>
Cc: dmaengine@vger.kernel.org, linux-serial@vger.kernel.org,
	vkoul@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v7 07/10] dmaengine: dw: report residue for queued transfers
Date: Sun, 15 Nov 2026 07:29:26 +0000	[thread overview]
Message-ID: <sashiko-outbox-215259@kernel.org> (raw)
In-Reply-To: <20261115-submit-dw-dma-synchronize-v1-v7-7-8d58f3d49e4d@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] dmaengine: dw: Fixes trailer cites 3bfb1d20b547 instead of
  b68fd0976286
--

commit cea2bb9706ea8fb5c7af2045e48883b9d2da9184
Author: James Hilliard <james.hilliard1@gmail.com>

> dmaengine: dw: report residue for queued transfers
>
> A submitted transfer may still be queued behind the active transaction.
> dwc_find_desc() only searches the active list, so a status query reports
> zero residue for the queued cookie even though none of its data has been
> transferred.
>
> Search the queue as well. The status getter already reports total_len for
> a descriptor that is not the active transaction, giving queued transfers
> their full remaining length.
>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
> Fixes: 3bfb1d20b547 ("dmaengine: Driver for the Synopsys DesignWare DMA controller")
> Cc: stable@vger.kernel.org
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>

[Severity: Low]
Should the Fixes: tag point to b68fd0976286 ("dmaengine: dw: move residue
to a descriptor") instead?

Commit 3bfb1d20b547 ("dmaengine: Driver for the Synopsys DesignWare DMA
controller") did not have residue reporting or dwc_find_desc().  Commit
b68fd0976286 ("dmaengine: dw: move residue to a descriptor") added
dwc_find_desc() and the per-descriptor residue lookup, searching only
dwc->active_list after f336e42f73d9 ("dw_dmac: Move single descriptor
from dwc->queue to dwc->active_list in dwc_complete_all") had already
kept queued descriptors on dwc->queue.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261115-submit-dw-dma-synchronize-v1-v7-0-8d58f3d49e4d@gmail.com?part=7

  reply	other threads:[~2026-11-15  7:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-15  7:19 [PATCH v7 00/10] dmaengine: dw: serialize completion and termination James Hilliard
2026-11-15  7:19 ` [PATCH v7 01/10] dmaengine: dw: Fix XFER bit set, but channel not idle error James Hilliard
2026-11-15  7:19 ` [PATCH v7 02/10] dmaengine: dw: serialize error recovery with channel termination James Hilliard
2026-11-15  7:19 ` [PATCH v7 03/10] dmaengine: dw: complete cookies before releasing the channel lock James Hilliard
2026-11-15  7:19 ` [PATCH v7 04/10] dmaengine: dw: extract hardware-LLP residue calculation James Hilliard
2026-11-15  7:19 ` [PATCH v7 05/10] dmaengine: dw: calculate residue in the status getter James Hilliard
2026-11-15  7:31   ` sashiko-bot
2026-11-15  7:19 ` [PATCH v7 06/10] dmaengine: dw: simplify transfer-complete handling James Hilliard
2026-11-15  7:19 ` [PATCH v7 07/10] dmaengine: dw: report residue for queued transfers James Hilliard
2026-11-15  7:29   ` sashiko-bot [this message]
2026-11-15  7:19 ` [PATCH v7 08/10] dmaengine: dw: drain the tasklet before releasing channel resources James Hilliard
2026-11-15  7:19 ` [PATCH v7 09/10] dmaengine: dw: synchronize completion callbacks James Hilliard
2026-11-15  7:19 ` [PATCH v7 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=sashiko-outbox-215259@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=Frank.Li@kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=james.hilliard1@gmail.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --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