aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/leds
diff options
context:
space:
mode:
authorAlan Stern <stern@rowland.harvard.edu>2011-11-03 23:39:18 +0100
committerGreg Kroah-Hartman <gregkh@suse.de>2011-11-11 09:36:57 -0800
commit8dc9c7911421d8e45901ffaf483b5dca99cbb055 (patch)
tree70de5dd4f12c46cb2406e8eeeee1fea3f3a6b986 /Documentation/leds
parent2d92f691cd1a1be5cdefb10d559fdd7443d4df7a (diff)
downloadkernel_samsung_smdk4412-8dc9c7911421d8e45901ffaf483b5dca99cbb055.zip
kernel_samsung_smdk4412-8dc9c7911421d8e45901ffaf483b5dca99cbb055.tar.gz
kernel_samsung_smdk4412-8dc9c7911421d8e45901ffaf483b5dca99cbb055.tar.bz2
PM / Runtime: Automatically retry failed autosuspends
commit 886486b792e4f6f96d4fbe8ec5bf20811cab7d6a upstream. 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> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'Documentation/leds')
0 files changed, 0 insertions, 0 deletions