summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-sqlite.py
diff options
context:
space:
mode:
authorRazvan Heghedus <heghedus.razvan@gmail.com>2021-09-15 15:16:13 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-10-05 13:39:46 +0300
commitce3e90d5a0cdbcb2ddebbf9e4363e59fa779ad3a (patch)
tree01622631c73ca66205b1c74166f35f2e70dfabfe /tools/perf/scripts/python/export-to-sqlite.py
parentae9a6149884e04b3460bd9d7ffe29c5ec8d223d8 (diff)
downloadlinux-ce3e90d5a0cdbcb2ddebbf9e4363e59fa779ad3a.tar.xz
usb: misc: ehset: Workaround for "special" hubs
The USB2.0 spec chapter 11.24.2.13 says that the USB port which is going under test needs to be put in suspend state before sending the test command. Many hubs, don't enforce this precondition and they work fine without this step. But there are some "special" hubs, which requires to disable the port power before sending the test command. Because the USB spec mention that the port should be suspended, also do this step before sending the test command. This could rise the problem with other hubs which are not compliant with the spec and the test command will not work if the port is suspend. If such hubs are found, a similar workaround like the disable part could be implemented to skip the suspend port command. Signed-off-by: Razvan Heghedus <heghedus.razvan@gmail.com> Link: https://lore.kernel.org/r/20210915121615.3790-1-heghedus.razvan@gmail.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions