diff options
author | Bin Liu <b-liu@ti.com> | 2018-07-19 14:39:37 -0500 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-07-21 08:38:29 +0200 |
commit | 249a32b7eeb3edb6897dd38f89651a62163ac4ed (patch) | |
tree | 66fb6811f6d727c09d048b8401fda320c7d0ca43 /tools/usb/ffs-test.c | |
parent | d89b7664f76047e7beca8f07e86f2ccfad085a28 (diff) | |
download | linux-stable-249a32b7eeb3edb6897dd38f89651a62163ac4ed.tar.gz linux-stable-249a32b7eeb3edb6897dd38f89651a62163ac4ed.tar.bz2 linux-stable-249a32b7eeb3edb6897dd38f89651a62163ac4ed.zip |
usb: core: handle hub C_PORT_OVER_CURRENT condition
Based on USB2.0 Spec Section 11.12.5,
"If a hub has per-port power switching and per-port current limiting,
an over-current on one port may still cause the power on another port
to fall below specific minimums. In this case, the affected port is
placed in the Power-Off state and C_PORT_OVER_CURRENT is set for the
port, but PORT_OVER_CURRENT is not set."
so let's check C_PORT_OVER_CURRENT too for over current condition.
Fixes: 08d1dec6f405 ("usb:hub set hub->change_bits when over-current happens")
Cc: <stable@vger.kernel.org>
Tested-by: Alessandro Antenucci <antenucci@korg.it>
Signed-off-by: Bin Liu <b-liu@ti.com>
Acked-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/usb/ffs-test.c')
0 files changed, 0 insertions, 0 deletions