summaryrefslogtreecommitdiffstats
path: root/drivers/base/power/power.h
diff options
context:
space:
mode:
authorUlf Hansson2016-10-13 16:58:54 +0200
committerRafael J. Wysocki2016-11-19 00:15:39 +0100
commit1d9174fbc55ec99ccbfcafa3de2528ef78a849aa (patch)
tree7554f95445c5a71a76fd4a044e8a595b94471e89 /drivers/base/power/power.h
parentPM / Runtime: Don't allow to suspend a device with an active child (diff)
downloadkernel-qcow2-linux-1d9174fbc55ec99ccbfcafa3de2528ef78a849aa.tar.gz
kernel-qcow2-linux-1d9174fbc55ec99ccbfcafa3de2528ef78a849aa.tar.xz
kernel-qcow2-linux-1d9174fbc55ec99ccbfcafa3de2528ef78a849aa.zip
PM / Runtime: Defer resuming of the device in pm_runtime_force_resume()
When the pm_runtime_force_suspend|resume() helpers were invented, we still had CONFIG_PM_RUNTIME and CONFIG_PM_SLEEP as separate Kconfig options. To make sure these helpers worked for all combinations and without introducing too much of complexity, the device was always resumed in pm_runtime_force_resume(). More precisely, when CONFIG_PM_SLEEP was set and CONFIG_PM_RUNTIME was unset, we needed to resume the device as the subsystem/driver couldn't rely on using runtime PM to do it. As the CONFIG_PM_RUNTIME option was merged into CONFIG_PM a while ago, it removed this combination, of using CONFIG_PM_SLEEP without the earlier CONFIG_PM_RUNTIME. For this reason we can now rely on the subsystem/driver to use runtime PM to resume the device, instead of forcing that to be done in all cases. In other words, let's defer the runtime resume to a later point when it's actually needed. Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Tested-by: Marek Szyprowski <m.szyprowski@samsung.com> Tested-by: Geert Uytterhoeven <geert+renesas@glider.be> Acked-by: Kevin Hilman <khilman@baylibre.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/base/power/power.h')
0 files changed, 0 insertions, 0 deletions