mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2026-08-09 06:14:34 +02:00
Revert "spi: spi-cadence-quadspi: Fix pm runtime unbalance"
This reverts commitcdfb20e4b3which is commitb07f349d18upstream. There is cadence-qspi ff8d2000.spi: Unbalanced pm_runtime_enable! error without this revert. After reverting commitcdfb20e4b3("spi: spi-cadence-quadspi: Fix pm runtime unbalance") and commit1af6d1696c("spi: cadence-quadspi: fix cleanup of rx_chan on failure paths"), Unbalanced pm_runtime_enable! error does not appear. These two commits are backported from upstream commitb07f349d18("spi: spi-cadence-quadspi: Fix pm runtime unbalance") and commit04a8ff1bc3("spi: cadence-quadspi: fix cleanup of rx_chan on failure paths"). The commit04a8ff1bc3("spi: cadence-quadspi: fix cleanup of rx_chan on failure paths") fix commitb07f349d18("spi: spi-cadence-quadspi: Fix pm runtime unbalance"). The commitb07f349d18("spi: spi-cadence-quadspi: Fix pm runtime unbalance") fix commit86401132d7("spi: spi-cadence-quadspi: Fix missing unwind goto warnings"). The commit86401132d7("spi: spi-cadence-quadspi: Fix missing unwind goto warnings") fix commit0578a6dbfe("spi: spi-cadence-quadspi: add runtime pm support"). 6.6.y only backport commitb07f349d18("spi: spi-cadence-quadspi: Fix pm runtime unbalance") and commit04a8ff1bc3("spi: cadence-quadspi: fix cleanup of rx_chan on failure paths"), but does not backport commit0578a6dbfe("spi: spi-cadence-quadspi: add runtime pm support") and commit86401132d7("spi: spi-cadence-quadspi: Fix missing unwind goto warnings"). And the backport of commitb07f349d18("spi: spi-cadence-quadspi: Fix pm runtime unbalance") differs with the original patch. So there is Unbalanced pm_runtime_enable error. If revert the backport for commitb07f349d18("spi: spi-cadence-quadspi: Fix pm runtime unbalance") and commit04a8ff1bc3("spi: cadence-quadspi: fix cleanup of rx_chan on failure paths"), there is no error. If backport commit0578a6dbfe("spi: spi-cadence-quadspi: add runtime pm support") and commit86401132d7("spi: spi-cadence-quadspi: Fix missing unwind goto warnings"), there is hang during booting. I didn't find the cause of the hang. Since commit0578a6dbfe("spi: spi-cadence-quadspi: add runtime pm support") and commit86401132d7("spi: spi-cadence-quadspi: Fix missing unwind goto warnings") are not backported, commitb07f349d18("spi: spi-cadence-quadspi: Fix pm runtime unbalance") and commit04a8ff1bc3("spi: cadence-quadspi: fix cleanup of rx_chan on failure paths") are not needed. So revert commits commitcdfb20e4b3("spi: spi-cadence-quadspi: Fix pm runtime unbalance") and commit1af6d1696c("spi: cadence-quadspi: fix cleanup of rx_chan on failure paths"). Signed-off-by: Jinfeng Wang <jinfeng.wang.cn@windriver.com> Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
committed by
Greg Kroah-Hartman
parent
94f7d90703
commit
de6b545bcd
@@ -1868,13 +1868,6 @@ static int cqspi_probe(struct platform_device *pdev)
|
||||
goto probe_setup_failed;
|
||||
}
|
||||
|
||||
pm_runtime_enable(dev);
|
||||
|
||||
if (cqspi->rx_chan) {
|
||||
dma_release_channel(cqspi->rx_chan);
|
||||
goto probe_setup_failed;
|
||||
}
|
||||
|
||||
ret = spi_register_controller(host);
|
||||
if (ret) {
|
||||
dev_err(&pdev->dev, "failed to register SPI ctlr %d\n", ret);
|
||||
@@ -1884,7 +1877,6 @@ static int cqspi_probe(struct platform_device *pdev)
|
||||
return 0;
|
||||
probe_setup_failed:
|
||||
cqspi_controller_enable(cqspi, 0);
|
||||
pm_runtime_disable(dev);
|
||||
probe_reset_failed:
|
||||
if (cqspi->is_jh7110)
|
||||
cqspi_jh7110_disable_clk(pdev, cqspi);
|
||||
@@ -1906,8 +1898,7 @@ static void cqspi_remove(struct platform_device *pdev)
|
||||
if (cqspi->rx_chan)
|
||||
dma_release_channel(cqspi->rx_chan);
|
||||
|
||||
if (pm_runtime_get_sync(&pdev->dev) >= 0)
|
||||
clk_disable(cqspi->clk);
|
||||
clk_disable_unprepare(cqspi->clk);
|
||||
|
||||
if (cqspi->is_jh7110)
|
||||
cqspi_jh7110_disable_clk(pdev, cqspi);
|
||||
|
||||
Reference in New Issue
Block a user