9f6d8f6ab2
Currently, the PM core disables runtime PM for all devices right after executing subsystem/driver .suspend() callbacks for them and re-enables it right before executing subsystem/driver .resume() callbacks for them. This may lead to problems when there are two devices such that the .suspend() callback executed for one of them depends on runtime PM working for the other. In that case, if runtime PM has already been disabled for the second device, the first one's .suspend() won't work correctly (and analogously for resume). To make those issues go away, make the PM core disable runtime PM for devices right before executing subsystem/driver .suspend_late() callbacks for them and enable runtime PM for them right after executing subsystem/driver .resume_early() callbacks for them. This way the potential conflitcs between .suspend_late()/.resume_early() and their runtime PM counterparts are still prevented from happening, but the subtle ordering issues related to disabling/enabling runtime PM for devices during system suspend/resume are much easier to avoid. Reported-and-tested-by: Jan-Matthias Braun <jan_braun@gmx.net> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Reviewed-by: Ulf Hansson <ulf.hansson@linaro.org> Reviewed-by: Kevin Hilman <khilman@deeprootsystems.com> Cc: 3.4+ <stable@vger.kernel.org> |
||
|---|---|---|
| .. | ||
| regulator | ||
| 00-INDEX | ||
| apm-acpi.txt | ||
| basic-pm-debugging.txt | ||
| charger-manager.txt | ||
| devices.txt | ||
| drivers-testing.txt | ||
| freezing-of-tasks.txt | ||
| interface.txt | ||
| notifiers.txt | ||
| opp.txt | ||
| pci.txt | ||
| pm_qos_interface.txt | ||
| power_supply_class.txt | ||
| runtime_pm.txt | ||
| s2ram.txt | ||
| states.txt | ||
| suspend-and-cpuhotplug.txt | ||
| swsusp-and-swap-files.txt | ||
| swsusp-dmcrypt.txt | ||
| swsusp.txt | ||
| tricks.txt | ||
| userland-swsusp.txt | ||
| video_extension.txt | ||
| video.txt | ||