diff options
author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2016-05-20 23:09:49 +0200 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2016-05-20 23:09:49 +0200 |
commit | 3a17fb329da68cb00558721aff876a80bba2fdb9 (patch) | |
tree | ccd2f44a5496aa8d85437d9f17806c89f5fa7664 /kernel | |
parent | fba1fbf56383073d286e6e3657bff36ee0f410e8 (diff) | |
download | linux-3a17fb329da68cb00558721aff876a80bba2fdb9.tar.bz2 |
PM / sleep: Handle failures in device_suspend_late() consistently
Grygorii Strashko reports:
The PM runtime will be left disabled for the device if its
.suspend_late() callback fails and async suspend is not allowed
for this device. In this case device will not be added in
dpm_late_early_list and dpm_resume_early() will ignore this
device, as result PM runtime will be disabled for it forever
(side effect: after 8 subsequent failures for the same device
the PM runtime will be reenabled due to disable_depth overflow).
To fix this problem, add devices to dpm_late_early_list regardless
of whether or not device_suspend_late() returns errors for them.
That will ensure failures in there to be handled consistently for
all devices regardless of their async suspend/resume status.
Reported-by: Grygorii Strashko <grygorii.strashko@ti.com>
Tested-by: Grygorii Strashko <grygorii.strashko@ti.com>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Cc: All applicable <stable@vger.kernel.org>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions