summaryrefslogtreecommitdiffstats
path: root/drivers/usb/musb
diff options
context:
space:
mode:
authorAlan Stern <stern@rowland.harvard.edu>2010-06-22 16:14:48 -0400
committerGreg Kroah-Hartman <gregkh@suse.de>2010-06-30 08:16:06 -0700
commit48826626263d4a61d06fd8c5805da31f925aefa0 (patch)
tree8d00f7a24db086eed136d05d2bf07e37029b35ef /drivers/usb/musb
parent03ab7461df3c74c9418c3f5485ea1127ece1ff79 (diff)
downloadblackbird-op-linux-48826626263d4a61d06fd8c5805da31f925aefa0.tar.gz
blackbird-op-linux-48826626263d4a61d06fd8c5805da31f925aefa0.zip
USB: obey the sysfs power/wakeup setting
This patch (as1403) is a partial reversion of an earlier change (commit 5f677f1d45b2bf08085bbba7394392dfa586fa8e "USB: fix remote wakeup settings during system sleep"). After hearing from a user, I realized that remote wakeup should be enabled during system sleep whenever userspace allows it, and not only if a driver requests it too. Indeed, there could be a device with no driver, that does nothing but generate a wakeup request when the user presses a button. Such a device should be allowed to do its job. The problem fixed by the earlier patch -- device generating a wakeup request for no reason, causing system suspend to abort -- was also addressed by a later patch ("USB: don't enable remote wakeup by default", accepted but not yet merged into mainline). The device won't be able to generate the bogus wakeup requests because it will be disabled for remote wakeup by default. Hence this reversion will not re-introduce any old problems. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Cc: stable <stable@kernel.org> [.34] Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/usb/musb')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud