[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <72f49447-5c99-4028-90cf-3f5cc11e8b53@quicinc.com>
Date: Fri, 18 Apr 2025 17:39:50 +0530
From: Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>
To: Christophe JAILLET <christophe.jaillet@...adoo.fr>,
Mark Brown
<broonie@...nel.org>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Alexandre
Torgue <alexandre.torgue@...s.st.com>,
Patrice Chotard
<patrice.chotard@...s.st.com>
CC: <linux-kernel@...r.kernel.org>, <kernel-janitors@...r.kernel.org>,
<linux-spi@...r.kernel.org>,
<linux-stm32@...md-mailman.stormreply.com>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] spi: stm32-ospi: Fix an error handling path in
stm32_ospi_probe()
On 4/18/2025 4:57 PM, Christophe JAILLET wrote:
[...]
> diff --git a/drivers/spi/spi-stm32-ospi.c b/drivers/spi/spi-stm32-ospi.c
> index 668022098b1e..9ec9823409cc 100644
> --- a/drivers/spi/spi-stm32-ospi.c
> +++ b/drivers/spi/spi-stm32-ospi.c
> @@ -960,6 +960,10 @@ static int stm32_ospi_probe(struct platform_device *pdev)
> err_pm_enable:
> pm_runtime_force_suspend(ospi->dev);
> mutex_destroy(&ospi->lock);
> + if (ospi->dma_chtx)
> + dma_release_channel(ospi->dma_chtx);
why can't you move to devm_dma_request_chan ? No need to cleanup.
> + if (ospi->dma_chrx)
> + dma_release_channel(ospi->dma_chrx);
>
> return ret;
> }
Powered by blists - more mailing lists