From: Frank Li <Frank.li@oss.nxp.com>
To: Linus Walleij <linusw@kernel.org>
Cc: Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
dmaengine@vger.kernel.org, phone-devel@vger.kernel.org
Subject: Re: [PATCH v3 02/22] dmaengine: ste_dma40: Fix cyclic transfer residue
Date: Fri, 18 Sep 2026 16:41:52 -0500 [thread overview]
Message-ID: <aq2wIPJW6viUxyy9@SMW015318> (raw)
In-Reply-To: <20260918-dma40-fixes-v3-2-8dd8450669e8@kernel.org>
On Fri, Sep 18, 2026 at 06:24:21PM +0200, Linus Walleij wrote:
> DMA40 reads residue from the element count of the currently active LLI.
> For a cyclic transfer this reports at most one period, not the bytes
> remaining until the cyclic buffer wraps.
>
> Once DMA40 advertises burst granularity, DMAengine PCM uses this residue
> directly. For a four-period PCM buffer it consequently reports the
> hardware pointer near three periods after every period interrupt. ALSA
> eventually stops playback with -EIO although DMA period callbacks
> continue.
>
> Track the active period of cyclic descriptors and add all later periods
> in the buffer to the current LLI residue. Update the active period in the
> terminal-count interrupt before scheduling its callback so residue also
> stays coherent around period boundaries.
>
> Also reject invalid cyclic geometries before dividing or constructing
> the scatterlist.
>
> Fixes: 15c606686541 ("dmaengine: ste_dma40: indicate granularity on channels")
> Assisted-by: LLM
> Signed-off-by: Linus Walleij <linusw@kernel.org>
> ---
> drivers/dma/ste_dma40.c | 42 +++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 39 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/dma/ste_dma40.c b/drivers/dma/ste_dma40.c
> index e4d689c9eba8..49e9139e0ad0 100644
> --- a/drivers/dma/ste_dma40.c
> +++ b/drivers/dma/ste_dma40.c
> @@ -378,6 +378,9 @@ struct d40_lli_pool {
> * @lli_len: Number of llis of current descriptor.
> * @lli_current: Number of transferred llis.
> * @lcla_alloc: Number of LCLA entries allocated.
> + * @cyclic_buf_len: Length of the cyclic buffer.
> + * @cyclic_period_len: Length of one cyclic period.
> + * @cyclic_pos: Start of the current cyclic period in the buffer.
> * @txd: DMA engine struct. Used for among other things for communication
> * during a transfer.
> * @node: List entry.
> @@ -396,6 +399,9 @@ struct d40_desc {
> int lli_len;
> int lli_current;
> int lcla_alloc;
> + size_t cyclic_buf_len;
> + size_t cyclic_period_len;
> + size_t cyclic_pos;
>
> struct dma_async_tx_descriptor txd;
> struct list_head node;
> @@ -1566,6 +1572,12 @@ static void dma_tc_handle(struct d40_chan *d40c)
> if (d40d->lli_current == d40d->lli_len)
> d40d->lli_current = 0;
> }
> +
> + if (d40d->cyclic_period_len) {
> + d40d->cyclic_pos += d40d->cyclic_period_len;
You depend irq handle will be called every period.
if period is short, like 100us, is it possible hardware combine twice or
more irq to once, cause miss count cyclic_pos?
> + if (d40d->cyclic_pos >= d40d->cyclic_buf_len)
> + d40d->cyclic_pos = 0;
> + }
> } else {
> d40_lcla_free_all(d40c, d40d);
>
> @@ -2108,15 +2120,27 @@ static bool d40_is_paused(struct d40_chan *d40c)
>
> }
>
> -static u32 stedma40_residue(struct dma_chan *chan)
> +static u32 stedma40_residue(struct dma_chan *chan, dma_cookie_t cookie)
> {
> struct d40_chan *d40c =
> container_of(chan, struct d40_chan, chan);
> + struct d40_desc *d40d;
> u32 bytes_left;
> unsigned long flags;
>
> spin_lock_irqsave(&d40c->lock, flags);
> bytes_left = d40_residue(d40c);
> +
> + d40d = d40_first_active_get(d40c);
> + /*
> + * The hardware residue is for the current LLI. Cyclic transfers use
> + * one LLI for each period, so include the later periods in the buffer.
> + */
> + if (d40d && d40d->txd.cookie == cookie && d40d->cyclic &&
> + d40d->cyclic_period_len)
> + bytes_left += d40d->cyclic_buf_len - d40d->cyclic_pos -
> + d40d->cyclic_period_len;
> +
I have some confuse about this formular, what bytes_left = d40_residue(d40c);
d40_residue() read some register value, I am not sure what's means.
and why d40d->cyclic_period_len, d40d->cyclic_pos += d40d->cyclic_period_len;
pos should already consider cyclic_period_len.
Frank
> spin_unlock_irqrestore(&d40c->lock, flags);
>
> return bytes_left;
> @@ -2524,11 +2548,17 @@ dma40_prep_dma_cyclic(struct dma_chan *chan, dma_addr_t dma_addr,
> size_t buf_len, size_t period_len,
> enum dma_transfer_direction direction, unsigned long flags)
> {
> - unsigned int periods = buf_len / period_len;
> + unsigned int periods;
> struct dma_async_tx_descriptor *txd;
> + struct d40_desc *desc;
> struct scatterlist *sg;
> int i;
>
> + if (!buf_len || !period_len || buf_len % period_len)
> + return NULL;
> +
> + periods = buf_len / period_len;
> +
> sg = kzalloc_objs(struct scatterlist, periods + 1, GFP_NOWAIT);
> if (!sg)
> return NULL;
> @@ -2543,6 +2573,12 @@ dma40_prep_dma_cyclic(struct dma_chan *chan, dma_addr_t dma_addr,
>
> txd = d40_prep_sg(chan, sg, sg, periods, direction,
> DMA_PREP_INTERRUPT);
> + if (txd) {
> + desc = container_of(txd, struct d40_desc, txd);
> + desc->cyclic_buf_len = buf_len;
> + desc->cyclic_period_len = period_len;
> + desc->cyclic_pos = 0;
> + }
>
> kfree(sg);
>
> @@ -2563,7 +2599,7 @@ static enum dma_status d40_tx_status(struct dma_chan *chan,
>
> ret = dma_cookie_status(chan, cookie, txstate);
> if (ret != DMA_COMPLETE && txstate)
> - dma_set_residue(txstate, stedma40_residue(chan));
> + dma_set_residue(txstate, stedma40_residue(chan, cookie));
>
> if (d40_is_paused(d40c))
> ret = DMA_PAUSED;
>
> --
> 2.55.0
>
next prev parent reply other threads:[~2026-09-18 21:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 16:24 [PATCH v3 00/22] dmaengine: ste_dma40: Fix numerous accumulated bugs Linus Walleij
2026-09-18 16:24 ` [PATCH v3 01/22] dmaengine: ste_dma40: Fix physical cyclic capability Linus Walleij
2026-09-18 19:57 ` Frank Li
2026-09-18 16:24 ` [PATCH v3 02/22] dmaengine: ste_dma40: Fix cyclic transfer residue Linus Walleij
2026-09-18 16:44 ` sashiko-bot
2026-09-18 21:41 ` Frank Li [this message]
2026-09-18 16:24 ` [PATCH v3 03/22] dmaengine: ste_dma40: Fix failed start cleanup Linus Walleij
2026-09-18 16:24 ` [PATCH v3 04/22] dmaengine: ste_dma40: Fix probe runtime PM disable Linus Walleij
2026-09-18 16:24 ` [PATCH v3 05/22] dmaengine: ste_dma40: Check runtime PM in IRQ Linus Walleij
2026-09-18 16:24 ` [PATCH v3 06/22] dmaengine: ste_dma40: Handle runtime PM resume errors Linus Walleij
2026-09-18 16:37 ` sashiko-bot
2026-09-18 16:24 ` [PATCH v3 07/22] dmaengine: ste_dma40: Return IRQ_NONE without interrupt status Linus Walleij
2026-09-18 16:24 ` [PATCH v3 08/22] dmaengine: ste_dma40: Init hardware before registration Linus Walleij
2026-09-18 16:24 ` [PATCH v3 09/22] dmaengine: ste_dma40: Fix probe IRQ leak Linus Walleij
2026-09-18 16:24 ` [PATCH v3 10/22] dmaengine: ste_dma40: Fix DMA registration unwind Linus Walleij
2026-09-18 16:24 ` [PATCH v3 11/22] dmaengine: ste_dma40: Fix LCLA allocation order Linus Walleij
2026-09-18 16:24 ` [PATCH v3 12/22] dmaengine: ste_dma40: Fix probe LCLA free Linus Walleij
2026-09-18 16:24 ` [PATCH v3 13/22] dmaengine: ste_dma40: Put the LCPA SRAM node Linus Walleij
2026-09-18 16:24 ` [PATCH v3 14/22] dmaengine: ste_dma40: Fix memcpy channel parsing Linus Walleij
2026-09-18 16:24 ` [PATCH v3 15/22] dmaengine: ste_dma40: Validate disabled channel indexes Linus Walleij
2026-09-18 16:24 ` [PATCH v3 16/22] dmaengine: ste_dma40: Validate DMA specifier length Linus Walleij
2026-09-18 16:24 ` [PATCH v3 17/22] dmaengine: ste_dma40: Reject direction changes after allocation Linus Walleij
2026-09-18 16:24 ` [PATCH v3 18/22] dmaengine: ste_dma40: Fix logical channel bounds check Linus Walleij
2026-09-18 16:24 ` [PATCH v3 19/22] dmaengine: ste_dma40: Fix event group bounds Linus Walleij
2026-09-18 16:24 ` [PATCH v3 20/22] dmaengine: ste_dma40: Search all blocks for fixed logical channels Linus Walleij
2026-09-18 16:24 ` [PATCH v3 21/22] dmaengine: ste_dma40: Validate fixed physical channel indexes Linus Walleij
2026-09-18 16:24 ` [PATCH v3 22/22] dmaengine: ste_dma40: Validate memcpy configuration Linus Walleij
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=aq2wIPJW6viUxyy9@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linusw@kernel.org \
--cc=phone-devel@vger.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