summaryrefslogtreecommitdiff
path: root/crypto
diff options
context:
space:
mode:
authorMathias Nyman <mathias.nyman@linux.intel.com>2016-01-26 17:50:04 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-02-25 12:01:22 -0800
commitd15298509b86f06d63135770ac8433295a18375f (patch)
treee0e17f4c692892a0a76aa85a734acb924df7aa0d /crypto
parent2231e5748746cd57df389521397e1c7f91882077 (diff)
Revert "xhci: don't finish a TD if we get a short-transfer event mid TD"
commit a6835090716a85f2297668ba593bd00e1051e662 upstream. This reverts commit e210c422b6fd ("xhci: don't finish a TD if we get a short transfer event mid TD") Turns out that most host controllers do not follow the xHCI specs and never send the second event for the last TRB in the TD if there was a short event mid-TD. Returning the URB directly after the first short-transfer event is far better than never returning the URB. (class drivers usually timeout after 30sec). For the hosts that do send the second event we will go back to treating it as misplaced event and print an error message for it. The origial patch was sent to stable kernels and needs to be reverted from there as well Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions