diff options
author | Sarah Sharp <sarah.a.sharp@linux.intel.com> | 2009-08-27 14:36:03 -0700 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@suse.de> | 2009-10-05 09:32:49 -0700 |
commit | 9fa7825a00bb88d022a22d914646a1ce5e3ee5e0 (patch) | |
tree | cdcd8d8e0dc95467952a58046135c92443fac5a1 /block | |
parent | fed392f6ec5c09647298b23519e366b3526c55ac (diff) | |
download | linux-stable-9fa7825a00bb88d022a22d914646a1ce5e3ee5e0.tar.gz linux-stable-9fa7825a00bb88d022a22d914646a1ce5e3ee5e0.tar.bz2 linux-stable-9fa7825a00bb88d022a22d914646a1ce5e3ee5e0.zip |
USB: xhci: Handle babbling endpoints correctly.
commit 83fbcdcca03013bb5af130d6d91eba11e3d3269e upstream.
The 0.95 xHCI spec says that non-control endpoints will be halted if a
babble is detected on a transfer. The 0.96 xHCI spec says all types of
endpoints will be halted when a babble is detected. Some hardware that
claims to be 0.95 compliant halts the control endpoint anyway.
When a babble is detected on a control endpoint, check the hardware's
output endpoint context to see if the endpoint is marked as halted. If
the control endpoint is halted, a reset endpoint command must be issued
and the transfer ring dequeue pointer needs to be moved past the stopped
transfer. Basically, we treat it as if the control endpoint had stalled.
Handle bulk babbling endpoints as if we got a completion event with a
stall completion code.
Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'block')
0 files changed, 0 insertions, 0 deletions