From: Dave Jiang <dave.jiang@intel.com>
To: Lars-Peter Clausen <lars@metafoo.de>, Vinod Koul <vkoul@kernel.org>
Cc: dmaengine@vger.kernel.org
Subject: Re: [PATCH] dmaengine: dmaengine_desc_callback_valid(): Check for `callback_result`
Date: Sun, 24 Oct 2021 11:19:41 -0700 [thread overview]
Message-ID: <2570ae0c-c085-1e4e-cec6-6efab8106281@intel.com> (raw)
In-Reply-To: <20211023134101.28042-1-lars@metafoo.de>
On 10/23/2021 6:41 AM, Lars-Peter Clausen wrote:
> Before the `callback_result` callback was introduced drivers coded their
> invocation to the callback in a similar way to:
>
> if (cb->callback) {
> spin_unlock(&dma->lock);
> cb->callback(cb->callback_param);
> spin_lock(&dma->lock);
> }
>
> With the introduction of `callback_result` two helpers where introduced to
> transparently handle both types of callbacks. And drivers where updated to
> look like this:
>
> if (dmaengine_desc_callback_valid(cb)) {
> spin_unlock(&dma->lock);
> dmaengine_desc_callback_invoke(cb, ...);
> spin_lock(&dma->lock);
> }
>
> dmaengine_desc_callback_invoke() correctly handles both `callback_result`
> and `callback`. But we forgot to update the dmaengine_desc_callback_valid()
> function to check for `callback_result`. As a result DMA descriptors that
> use the `callback_result` rather than `callback` don't have their callback
> invoked by drivers that follow the pattern above.
>
> Fix this by checking for both `callback` and `callback_result` in
> dmaengine_desc_callback_valid().
>
> Fixes: f067025bc676 ("dmaengine: add support to provide error result from a DMA transation")
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
Acked-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/dma/dmaengine.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma/dmaengine.h b/drivers/dma/dmaengine.h
> index 1bfbd64b1371..53f16d3f0029 100644
> --- a/drivers/dma/dmaengine.h
> +++ b/drivers/dma/dmaengine.h
> @@ -176,7 +176,7 @@ dmaengine_desc_get_callback_invoke(struct dma_async_tx_descriptor *tx,
> static inline bool
> dmaengine_desc_callback_valid(struct dmaengine_desc_callback *cb)
> {
> - return (cb->callback) ? true : false;
> + return cb->callback || cb->callback_result;
> }
>
> struct dma_chan *dma_get_slave_channel(struct dma_chan *chan);
next prev parent reply other threads:[~2021-10-24 18:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 13:41 [PATCH] dmaengine: dmaengine_desc_callback_valid(): Check for `callback_result` Lars-Peter Clausen
2021-10-24 18:19 ` Dave Jiang [this message]
2021-10-25 4:13 ` 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=2570ae0c-c085-1e4e-cec6-6efab8106281@intel.com \
--to=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=lars@metafoo.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.