spi: sprd: Don't skip cleanup in remove's error path

If pm_runtime_resume_and_get() failed before this change, two error
messages were printed. One directly in sprd_spi_remove() and another
by the device core as the return value is non-zero.

The better handling of a failure to resume the device is to do the
software related cleanup anyhow and only skip hardware accesses.
This leaves the device in an unknown state, but there is nothing that can
be done about that.

Even in the error case, return zero to suppress the device core's error
message.

Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Link: https://lore.kernel.org/r/20230307211426.2331483-2-u.kleine-koenig@pengutronix.de
Signed-off-by: Mark Brown <broonie@kernel.org>

diff --git a/drivers/spi/spi-sprd.c b/drivers/spi/spi-sprd.c
index 65b8075..45b69b8 100644 (file)
--- a/drivers/spi/spi-sprd.c
+++ b/drivers/spi/spi-sprd.c
@@ -1008,17 +1008,17 @@ static int sprd_spi_remove(struct platform_device *pdev)
        struct sprd_spi *ss = spi_controller_get_devdata(sctlr);
        int ret;
 
-       ret = pm_runtime_resume_and_get(ss->dev);
-       if (ret < 0) {
+       ret = pm_runtime_get_sync(ss->dev);
+       if (ret < 0)
                dev_err(ss->dev, "failed to resume SPI controller\n");
-               return ret;
-       }
 
        spi_controller_suspend(sctlr);
 
-       if (ss->dma.enable)
-               sprd_spi_dma_release(ss);
-       clk_disable_unprepare(ss->clk);
+       if (ret >= 0) {
+               if (ss->dma.enable)
+                       sprd_spi_dma_release(ss);
+               clk_disable_unprepare(ss->clk);
+       }
        pm_runtime_put_noidle(&pdev->dev);
        pm_runtime_disable(&pdev->dev);