| commit | 8c603fc5c6608bac3e3df537f8f4a70a24e4edd0 | |
| author | Alan Stern <stern@rowland.harvard.edu> | |
| Wed, 15 Jun 2011 20:29:16 +0000 (15 16:29 -0400) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Sat, 9 Jul 2011 06:15:37 +0000 (8 23:15 -0700) | ||
| tree | 25108b8a9e36c9e6add1378adea22bbcde123f28 | treesnapshot (tar.gz zip) |
| parent | c4c3048b2bda6562bcdf5507bb9c6c248a87f675 | commitdiff |
USB: don't let the hub driver prevent system sleep
commit cbb330045e5df8f665ac60227ff898421fc8fb92 upstream.
This patch (as1465) continues implementation of the policy that errors
during suspend or hibernation should not prevent the system from going
to sleep.
In this case, failure to turn on the Suspend feature for a hub port
shouldn't be reported as an error. There are situations where this
does actually occur (such as when the device plugged into that port
was disconnected in the recent past), and it turns out to be harmless.
There's no reason for it to prevent a system sleep.
Also, don't allow the hub driver to fail a system suspend if the
downstream ports aren't all suspended. This is also harmless (and
should never happen, given the change mentioned above); printing a
warning message in the kernel log is all we really need to do.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit cbb330045e5df8f665ac60227ff898421fc8fb92 upstream.
This patch (as1465) continues implementation of the policy that errors
during suspend or hibernation should not prevent the system from going
to sleep.
In this case, failure to turn on the Suspend feature for a hub port
shouldn't be reported as an error. There are situations where this
does actually occur (such as when the device plugged into that port
was disconnected in the recent past), and it turns out to be harmless.
There's no reason for it to prevent a system sleep.
Also, don't allow the hub driver to fail a system suspend if the
downstream ports aren't all suspended. This is also harmless (and
should never happen, given the change mentioned above); printing a
warning message in the kernel log is all we really need to do.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/usb/core/hub.c | diffblobblamehistory |