diff options
| author | Shen Guang <shenguang10@gmail.com> | 2014-01-08 10:45:42 +0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-01-09 03:01:11 +0400 |
| commit | 08d1dec6f4054e3613f32051d9b149d4203ce0d2 (patch) | |
| tree | 74441f57ac7c61700c08e78d66d2ae764d6b26dd /crypto/salsa20_generic.c | |
| parent | ac5166bcdb43889a5bd837f5076b78049e1f8bca (diff) | |
| download | linux-08d1dec6f4054e3613f32051d9b149d4203ce0d2.tar.xz | |
usb:hub set hub->change_bits when over-current happens
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'crypto/salsa20_generic.c')
0 files changed, 0 insertions, 0 deletions