diff options
author | Tony Lindgren <tony@atomide.com> | 2016-02-10 15:02:45 -0800 |
---|---|---|
committer | Wolfram Sang <wsa@the-dreams.de> | 2016-02-12 19:42:31 +0100 |
commit | e6244deed843bc001697f37e5beb1c0daf4f46a4 (patch) | |
tree | c93785340b7aba4fe82187b1524f5390f1d703a1 /drivers/i2c/busses/i2c-uniphier.c | |
parent | 388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95 (diff) | |
download | linux-e6244deed843bc001697f37e5beb1c0daf4f46a4.tar.gz linux-e6244deed843bc001697f37e5beb1c0daf4f46a4.tar.bz2 linux-e6244deed843bc001697f37e5beb1c0daf4f46a4.zip |
i2c: omap: Fix PM regression with deferred probe for pm_runtime_reinit
Commit 5de85b9d57ab ("PM / runtime: Re-init runtime PM states at probe
error and driver unbind") introduced pm_runtime_reinit() that is used
to reinitialize PM runtime after -EPROBE_DEFER. This allows shutting
down the device after a failed probe.
However, for drivers using pm_runtime_use_autosuspend() this can cause
a state where suspend callback is never called after -EPROBE_DEFER.
On the following device driver probe, hardware state is different from
the PM runtime state causing omap_device to produce the following
error:
omap_device_enable() called from invalid state 1
And with omap_device and omap hardware being picky for PM, this will
block any deeper idle states in hardware.
The solution is to fix the drivers to follow the PM runtime documentation:
1. For sections of code that needs the device disabled, use
pm_runtime_put_sync_suspend() if pm_runtime_set_autosuspend() has
been set.
2. For driver exit code, use pm_runtime_dont_use_autosuspend() before
pm_runtime_put_sync() if pm_runtime_use_autosuspend() has been
set.
Fixes: 5de85b9d57ab ("PM / runtime: Re-init runtime PM states at probe
error and driver unbind")
Signed-off-by: Tony Lindgren <tony@atomide.com>
Acked-by: Ulf Hansson <ulf.hansson@linaro.org>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Diffstat (limited to 'drivers/i2c/busses/i2c-uniphier.c')
0 files changed, 0 insertions, 0 deletions