Re: PM regression with commit 5de85b9d57ab PM runtime re-init in v4.5-rc1
From: Tony Lindgren <tony@atomide.com>
Date: 2016-01-26 22:50:13
Also in:
linux-arm-kernel, linux-omap
* Tony Lindgren [off-list ref] [160126 14:49]:
Hi,
Looks like commit 5de85b9d57ab ("PM / runtime: Re-init runtime
PM states at probe error and driver unbind") broke PM on at least
omap3. It seems we now need to additionally also call
pm_runtime_dont_use_autosuspend() to get things working again?
The following fixes idling on omap3, but I'm wondering if we
should do something in pm_runtime_reinit() instead?Oh one more thing, this happens as we get -EPROBE_DEFER with the regulators initially.
quoted hunk ↗ jump to hunk
8< ------------------------ a/drivers/mmc/host/omap_hsmmc.c +++ b/drivers/mmc/host/omap_hsmmc.c@@ -2232,6 +2232,7 @@ err_irq: dma_release_channel(host->tx_chan); if (host->rx_chan) dma_release_channel(host->rx_chan); + pm_runtime_dont_use_autosuspend(host->dev); pm_runtime_put_sync(host->dev); pm_runtime_disable(host->dev); if (host->dbclk) --To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html