linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: <Tudor.Ambarus@microchip.com>
To: <andriy.shevchenko@linux.intel.com>, <vkoul@kernel.org>,
	<Nicolas.Ferre@microchip.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <Ludovic.Desroches@microchip.com>
Subject: Re: [PATCH v1 1/2] at_hdmac: check and return DMA_PAUSED status when suitable
Date: Tue, 8 Nov 2022 11:50:19 +0000	[thread overview]
Message-ID: <d3d93452-70e6-72e5-b28e-1b259d1e489c@microchip.com> (raw)
In-Reply-To: <20221108074938.48853-1-andriy.shevchenko@linux.intel.com>

Hi, Andy,

On 11/8/22 09:49, Andy Shevchenko wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> device_tx_status() may return DMA_PAUSED status when driver supports it.

Yeah, but you haven't described the why. And that's because dma_cookie_status()
currently considers just DMA_COMPLETE and DMA_IN_PROGRESS for the status of the
cookie, so the controller drivers are forced to query the DMA_PAUSED state
themselves.

Also, I noticed that Vinod prefers that you use the full paragraph in the commit
message, and not a continuation of the patch title, so you may want to reword
the commit message.

> 
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>  drivers/dma/at_hdmac.c | 15 ++++++++++++++-
>  1 file changed, 14 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/dma/at_hdmac.c b/drivers/dma/at_hdmac.c
> index 8858470246e1..a9d8dd990d6e 100644
> --- a/drivers/dma/at_hdmac.c
> +++ b/drivers/dma/at_hdmac.c
> @@ -1669,9 +1669,19 @@ atc_tx_status(struct dma_chan *chan,
>         int ret;
> 
>         dma_status = dma_cookie_status(chan, cookie, txstate);
> -       if (dma_status == DMA_COMPLETE || !txstate)
> +       if (dma_status == DMA_COMPLETE)
>                 return dma_status;
> 
> +       /*
> +        * There's no point in calculating the residue if there's
> +        * no txstate to store the value.
> +        */
> +       if (!txstate) {
> +               if (test_bit(ATC_IS_PAUSED, &atchan->status))

there's a helper function that you can use instead: atc_chan_is_paused()

> +                       return DMA_PAUSED;
> +               return DMA_ERROR;

return dma_status please

> +       }
> +
>         spin_lock_irqsave(&atchan->vc.lock, flags);
>         /*  Get number of bytes left in the active transactions */
>         ret = atc_get_residue(chan, cookie, &residue);
> @@ -1684,6 +1694,9 @@ atc_tx_status(struct dma_chan *chan,
>                 dma_set_residue(txstate, residue);
>         }
> 
> +       if (test_bit(ATC_IS_PAUSED, &atchan->status))

The status may change after spin_unlock_irqrestore(). Should the residue
be in sync with the dma status? If yes, you should check the status while
holding the lock.

> +               dma_status = DMA_PAUSED;
> +
>         dev_vdbg(chan2dev(chan), "tx_status %d: cookie = %d residue = %u\n",
>                  dma_status, cookie, residue);
> 
> --
> 2.35.1
> 

-- 
Cheers,
ta

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-11-08 11:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08  7:49 [PATCH v1 1/2] at_hdmac: check and return DMA_PAUSED status when suitable Andy Shevchenko
2022-11-08  7:49 ` [PATCH v1 2/2] at_hdmac: return actual status when txstatus parameter is NULL Andy Shevchenko
2022-11-08 11:51   ` Tudor.Ambarus
2022-11-08 11:50 ` Tudor.Ambarus [this message]
2022-11-08 12:18   ` [PATCH v1 1/2] at_hdmac: check and return DMA_PAUSED status when suitable Andy Shevchenko

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=d3d93452-70e6-72e5-b28e-1b259d1e489c@microchip.com \
    --to=tudor.ambarus@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).