diff options
author | Paul Zimmerman <Paul.Zimmerman@synopsys.com> | 2010-11-17 16:26:50 -0800 |
---|---|---|
committer | Sarah Sharp <sarah.a.sharp@linux.intel.com> | 2010-11-19 16:23:07 -0800 |
commit | 7a3783efffc7bc2e702d774e47fad5b8e37e9ad1 (patch) | |
tree | 1801a42bf73c4ae674dc149c6669100fdd8e10cc /security | |
parent | 02e2c51ba3e80acde600721ea784c3ef84da5ea1 (diff) | |
download | kernel_samsung_aries-7a3783efffc7bc2e702d774e47fad5b8e37e9ad1.zip kernel_samsung_aries-7a3783efffc7bc2e702d774e47fad5b8e37e9ad1.tar.gz kernel_samsung_aries-7a3783efffc7bc2e702d774e47fad5b8e37e9ad1.tar.bz2 |
xhci: Fix reset-device and configure-endpoint commands
We have been having problems with the USB-IF Gold Tree tests when plugging
and unplugging devices from the tree. I have seen that the reset-device
and configure-endpoint commands, which are invoked from
xhci_discover_or_reset_device() and xhci_configure_endpoint(), will sometimes
time out.
After much debugging, I determined that the commands themselves do not actually
time out, but rather their completion events do not get delivered to the right
place.
This happens when the command ring has just wrapped around, and it's enqueue
pointer is left pointing to the link TRB. xhci_discover_or_reset_device() and
xhci_configure_endpoint() use the enqueue pointer directly as their command
TRB pointer, without checking whether it's pointing to the link TRB.
When the completion event arrives, if the command TRB is pointing to the link
TRB, the check against the command ring dequeue pointer in
handle_cmd_in_cmd_wait_list() fails, so the completion inside the command does
not get signaled.
The patch below fixes the timeout problem for me.
This should be queued for the 2.6.35 and 2.6.36 stable trees.
Signed-off-by: Paul Zimmerman <paulz@synopsys.com>
Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: stable@kernel.org
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions