summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorAlan Stern <stern@rowland.harvard.edu>2011-12-06 23:24:52 +0100
committerRafael J. Wysocki <rjw@sisk.pl>2011-12-07 22:26:56 +0100
commitfe6b91f47080eb17d21cbf2a39311877d57f6938 (patch)
tree0c63640274b02fdb3c95546cf966896e97bb5877 /Documentation
parentb835c0f47f725d864bf2545f10c733b754bb6d51 (diff)
downloadop-kernel-dev-fe6b91f47080eb17d21cbf2a39311877d57f6938.zip
op-kernel-dev-fe6b91f47080eb17d21cbf2a39311877d57f6938.tar.gz
PM / Driver core: leave runtime PM enabled during system shutdown
Disabling all runtime PM during system shutdown turns out not to be a good idea, because some devices may need to be woken up from a low-power state at that time. The whole point of disabling runtime PM for system shutdown was to prevent untimely runtime-suspend method calls. This patch (as1504) accomplishes the same result by incrementing the usage count for each device and waiting for ongoing runtime-PM callbacks to finish. This is what we already do during system suspend and hibernation, which makes sense since the shutdown method is pretty much a legacy analog of the pm->poweroff method. This fixes a recent regression on some OMAP systems introduced by commit af8db1508f2c9f3b6e633e2d2d906c6557c617f9 (PM / driver core: disable device's runtime PM during shutdown). Reported-and-tested-by: NeilBrown <neilb@suse.de> Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Acked-by: Greg Kroah-Hartman <gregkh@suse.de> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud