diff options
author | Shen Guang <shenguang10@gmail.com> | 2014-01-08 14:45:42 +0800 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-10-05 14:54:10 -0700 |
commit | 47415d5452b8945bfbe7e2adb3fa15658b3c3d21 (patch) | |
tree | 08a351ea487bc176bdb5f2d900259ebc047f51db /fs/afs/callback.c | |
parent | e5330465e2dd7cf08d6129389324b32c09e16028 (diff) | |
download | linux-3.10-47415d5452b8945bfbe7e2adb3fa15658b3c3d21.tar.gz linux-3.10-47415d5452b8945bfbe7e2adb3fa15658b3c3d21.tar.bz2 linux-3.10-47415d5452b8945bfbe7e2adb3fa15658b3c3d21.zip |
usb:hub set hub->change_bits when over-current happens
commit 08d1dec6f4054e3613f32051d9b149d4203ce0d2 upstream.
When we are doing compliance test with xHCI, we found that if we
enable CONFIG_USB_SUSPEND and plug in a bad device which causes
over-current condition to the root port, software will not be noticed.
The reason is that current code don't set hub->change_bits in
hub_activate() when over-current happens, and then hub_events() will
not check the port status because it thinks nothing changed.
If CONFIG_USB_SUSPEND is disabled, the interrupt pipe of the hub will
report the change and set hub->event_bits, and then hub_events() will
check what events happened.In this case over-current can be detected.
Signed-off-by: Shen Guang <shenguang10@gmail.com>
Acked-by: Alan Stern <stern@rowland.harvard.edu>
Acked-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Frans Klaver <fransklaver@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/afs/callback.c')
0 files changed, 0 insertions, 0 deletions