diff options
author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2017-11-16 22:51:22 +0100 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2017-11-16 22:51:22 +0100 |
commit | f8817f61e8215b0ff1b73a0d33fa04ef9e6bce8b (patch) | |
tree | 6c90b8f2ee96d1a384f96f437e05d4d937a7fdae /ipc | |
parent | bd2cd7d5a8f83ddc761025f42a3ca8e56351a6cc (diff) | |
download | linux-stable-f8817f61e8215b0ff1b73a0d33fa04ef9e6bce8b.tar.gz linux-stable-f8817f61e8215b0ff1b73a0d33fa04ef9e6bce8b.tar.bz2 linux-stable-f8817f61e8215b0ff1b73a0d33fa04ef9e6bce8b.zip |
PM / runtime: Drop children check from __pm_runtime_set_status()
The check for "active" children in __pm_runtime_set_status(), when
trying to set the parent device status to "suspended", doesn't
really make sense, because in fact it is not invalid to set the
status of a device with runtime PM disabled to "suspended" in any
case. It is invalid to enable runtime PM for a device with its
status set to "suspended" while its child_count reference counter
is nonzero, but the check in __pm_runtime_set_status() doesn't
really cover that situation.
For this reason, drop the children check from __pm_runtime_set_status()
and add a check against child_count reference counters of "suspended"
devices to pm_runtime_enable().
Fixes: a8636c89648a (PM / Runtime: Don't allow to suspend a device with an active child)
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org>
Reviewed-by: Johan Hovold <johan@kernel.org>
Diffstat (limited to 'ipc')
0 files changed, 0 insertions, 0 deletions