aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/usb/core/driver.c
diff options
context:
space:
mode:
authorAlan Stern <stern@rowland.harvard.edu>2011-11-03 23:39:18 +0100
committerRafael J. Wysocki <rjw@sisk.pl>2011-11-04 22:28:14 +0100
commit886486b792e4f6f96d4fbe8ec5bf20811cab7d6a (patch)
tree1c638e14492c16f8f69ca71fa93b2d81d8e4eeb6 /drivers/usb/core/driver.c
parent6513fd6972f725291ee8ce62c7a39fb8a6c7391e (diff)
downloadkernel_samsung_smdk4412-886486b792e4f6f96d4fbe8ec5bf20811cab7d6a.zip
kernel_samsung_smdk4412-886486b792e4f6f96d4fbe8ec5bf20811cab7d6a.tar.gz
kernel_samsung_smdk4412-886486b792e4f6f96d4fbe8ec5bf20811cab7d6a.tar.bz2
PM / Runtime: Automatically retry failed autosuspends
Originally, the runtime PM core would send an idle notification whenever a suspend attempt failed. The idle callback routine could then schedule a delayed suspend for some time later. However this behavior was changed by commit f71648d73c1650b8b4aceb3856bebbde6daa3b86 (PM / Runtime: Remove idle notification after failing suspend). No notifications were sent, and there was no clear mechanism to retry failed suspends. This caused problems for the usbhid driver, because it fails autosuspend attempts as long as a key is being held down. Therefore this patch (as1492) adds a mechanism for retrying failed autosuspends. If the callback routine updates the last_busy field so that the next autosuspend expiration time is in the future, the autosuspend will automatically be rescheduled. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Tested-by: Henrik Rydberg <rydberg@euromail.se> Cc: <stable@kernel.org> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Diffstat (limited to 'drivers/usb/core/driver.c')
0 files changed, 0 insertions, 0 deletions