From: sashiko-bot@kernel.org
To: Frank.Li@oss.nxp.com,
"open list:FREESCALE DSPI DRIVER" <imx@lists.linux.dev>,
"open list:ARM/Allwinner sunXi SoC support"
<linux-sunxi@lists.linux.dev>
Cc: Frank.Li@kernel.org, wsa+renesas@sang-engineering.com
Subject: Re: [PATCH 1/1] spi: use dmaengine_desc_set_callback()
Date: Mon, 02 Nov 2026 17:45:19 +0000 [thread overview]
Message-ID: <sashiko-outbox-193858@kernel.org> (raw)
In-Reply-To: <20261102174005.3933649-1-Frank.Li@oss.nxp.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] spi: rspi: missed desc_tx->callback conversion in rspi_dma_transfer()
--
commit fc7630df2ca55b14f36e688b27950bd8acaa67b6
Author: Frank Li <Frank.Li@nxp.com>
spi: use dmaengine_desc_set_callback()
This commit replaces open-coded assignments to the callback and
callback_param fields of struct dma_async_tx_descriptor with calls to
dmaengine_desc_set_callback() across SPI bus drivers in preparation for
making struct dma_async_tx_descriptor private to the DMA engine.
> diff --git a/drivers/spi/spi-rspi.c b/drivers/spi/spi-rspi.c
> index c61edd1c1353b..5e03a186e9e79 100644
> --- a/drivers/spi/spi-rspi.c
> +++ b/drivers/spi/spi-rspi.c
[ ... ]
> @@ -577,8 +576,7 @@ static int rspi_dma_transfer(struct rspi_data *rspi, struct sg_table *tx,
> /* No callback */
> desc_tx->callback = NULL;
> } else {
> - desc_tx->callback = rspi_dma_complete;
> - desc_tx->callback_param = rspi;
> + dmaengine_desc_set_callback(desc_tx, rspi_dma_complete, NULL, rspi);
> }
[Severity: Low]
In rspi_dma_transfer(), when both tx and rx scatter-gather tables are
present, the if (rx) branch right above the converted else branch still
directly assigns desc_tx->callback = NULL.
Should that branch also use dmaengine_desc_set_callback(desc_tx, NULL,
NULL, NULL) so that drivers/spi/spi-rspi.c does not fail to build when
struct dma_async_tx_descriptor is made private to the DMA engine?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261102174005.3933649-1-Frank.Li@oss.nxp.com?part=1
next prev parent reply other threads:[~2026-11-02 17:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 17:39 [PATCH 1/1] spi: use dmaengine_desc_set_callback() Frank.Li
2026-11-02 17:45 ` sashiko-bot [this message]
2026-11-03 9:04 ` Linus Walleij
2026-11-03 11:53 ` Mukesh Savaliya
2026-11-03 13:05 ` Alain Volmat
2026-11-03 14:00 ` Lad, Prabhakar
2026-11-03 16:49 ` Wolfram Sang
2026-11-04 1:04 ` Troy Mitchell
2026-11-04 1:58 ` Kunihiko Hayashi
2026-11-04 13:06 ` Thierry Reding
2026-11-04 13:23 ` Thierry Reding
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-193858@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=Frank.Li@oss.nxp.com \
--cc=imx@lists.linux.dev \
--cc=linux-sunxi@lists.linux.dev \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wsa+renesas@sang-engineering.com \
/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