mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frank Li <Frank.li@nxp.com>
To: Han Xu <han.xu@nxp.com>
Cc: Mark Brown <broonie@kernel.org>,
	John Ogness <john.ogness@linutronix.de>,
	Volker Haspel <volker.haspel@linutronix.de>,
	stable@vger.kernel.org, Kevin Hao <haokexin@gmail.com>,
	linux-spi@vger.kernel.org, imx@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: fsl-qspi: use devm function instead of driver remove
Date: Thu, 27 Mar 2025 11:45:24 -0400	[thread overview]
Message-ID: <Z+VylBMSnQVHFSV5@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250326224152.2147099-1-han.xu@nxp.com>

On Wed, Mar 26, 2025 at 05:41:51PM -0500, Han Xu wrote:
> Driver use devm APIs to manage clk/irq/resources and register the spi
> controller, but the legacy remove function will be called first during
> device detach and trigger kernel panic. Drop the remove function and use
> devm_add_action_or_reset() for driver cleanup to ensure the release
> sequence.
>
> Trigger kernel panic on i.MX8MQ by
> echo 30bb0000.spi >/sys/bus/platform/drivers/fsl-quadspi/unbind
>
> Cc: stable@vger.kernel.org
> Fixes: 8fcb830a00f0 ("spi: spi-fsl-qspi: use devm_spi_register_controller")
> Reported-by: Kevin Hao <haokexin@gmail.com>
> Signed-off-by: Han Xu <han.xu@nxp.com>

Reviewed-by: Frank Li <Frank.Li@nxp.com>

> ---
>  drivers/spi/spi-fsl-qspi.c | 31 +++++++++++++++++--------------
>  1 file changed, 17 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/spi/spi-fsl-qspi.c b/drivers/spi/spi-fsl-qspi.c
> index 355e6a39fb418..5c59fddb32c1b 100644
> --- a/drivers/spi/spi-fsl-qspi.c
> +++ b/drivers/spi/spi-fsl-qspi.c
> @@ -844,6 +844,19 @@ static const struct spi_controller_mem_caps fsl_qspi_mem_caps = {
>  	.per_op_freq = true,
>  };
>
> +static void fsl_qspi_cleanup(void *data)
> +{
> +	struct fsl_qspi *q = data;
> +
> +	/* disable the hardware */
> +	qspi_writel(q, QUADSPI_MCR_MDIS_MASK, q->iobase + QUADSPI_MCR);
> +	qspi_writel(q, 0x0, q->iobase + QUADSPI_RSER);
> +
> +	fsl_qspi_clk_disable_unprep(q);
> +
> +	mutex_destroy(&q->lock);
> +}
> +
>  static int fsl_qspi_probe(struct platform_device *pdev)
>  {
>  	struct spi_controller *ctlr;
> @@ -934,6 +947,10 @@ static int fsl_qspi_probe(struct platform_device *pdev)
>
>  	ctlr->dev.of_node = np;
>
> +	ret = devm_add_action_or_reset(dev, fsl_qspi_cleanup, q);
> +	if (ret)
> +		goto err_destroy_mutex;
> +

Look like needn't goto err_destroy_mutex. it should be enough

	if (ret)
		return ret;

Orginal error path:

err_destroy_mutex:
        mutex_destroy(&q->lock);    // already in fsl_qspi_cleanup()

err_disable_clk:
        fsl_qspi_clk_disable_unprep(q); // already in fsl_qspi_cleanup()

err_put_ctrl:
        spi_controller_put(ctlr); // suppose it is wrong, devm_spi_register_controller()
should consider it.


Frank

>  	ret = devm_spi_register_controller(dev, ctlr);
>  	if (ret)
>  		goto err_destroy_mutex;
> @@ -953,19 +970,6 @@ static int fsl_qspi_probe(struct platform_device *pdev)
>  	return ret;
>  }
>
> -static void fsl_qspi_remove(struct platform_device *pdev)
> -{
> -	struct fsl_qspi *q = platform_get_drvdata(pdev);
> -
> -	/* disable the hardware */
> -	qspi_writel(q, QUADSPI_MCR_MDIS_MASK, q->iobase + QUADSPI_MCR);
> -	qspi_writel(q, 0x0, q->iobase + QUADSPI_RSER);
> -
> -	fsl_qspi_clk_disable_unprep(q);
> -
> -	mutex_destroy(&q->lock);
> -}
> -
>  static int fsl_qspi_suspend(struct device *dev)
>  {
>  	return 0;
> @@ -1003,7 +1007,6 @@ static struct platform_driver fsl_qspi_driver = {
>  		.pm =   &fsl_qspi_pm_ops,
>  	},
>  	.probe          = fsl_qspi_probe,
> -	.remove		= fsl_qspi_remove,
>  };
>  module_platform_driver(fsl_qspi_driver);
>
> --
> 2.34.1
>

  reply	other threads:[~2025-03-27 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 22:41 Han Xu
2025-03-27 15:45 ` Frank Li [this message]
2025-03-27 21:11 ` Mark Brown

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=Z+VylBMSnQVHFSV5@lizhi-Precision-Tower-5810 \
    --to=frank.li@nxp.com \
    --cc=broonie@kernel.org \
    --cc=han.xu@nxp.com \
    --cc=haokexin@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=volker.haspel@linutronix.de \
    /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

all inboxes | Powered by JetHome®