summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorMathias Nyman <mathias.nyman@linux.intel.com>2019-12-11 16:20:06 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2019-12-17 20:39:08 +0100
commit8d0b11b6ac68f280aabe962349678342f0dcc297 (patch)
tree5cedfe2c584e06d650270a4939fed339e300ca0d /arch
parent6b399e679da42f76abdeab9722e687a61bb581f5 (diff)
xhci: handle some XHCI_TRUST_TX_LENGTH quirks cases as default behaviour.
commit 7ff11162808cc2ec66353fc012c58bb449c892c3 upstream. xhci driver claims it needs XHCI_TRUST_TX_LENGTH quirk for both Broadcom/Cavium and a Renesas xHC controllers. The quirk was inteded for handling false "success" complete event for transfers that had data left untransferred. These transfers should complete with "short packet" events instead. In these two new cases the false "success" completion is reported after a "short packet" if the TD consists of several TRBs. xHCI specs 4.10.1.1.2 say remaining TRBs should report "short packet" as well after the first short packet in a TD, but this issue seems so common it doesn't make sense to add the quirk for all vendors. Turn these events into short packets automatically instead. This gets rid of the "The WARN Successful completion on short TX for slot 1 ep 1: needs XHCI_TRUST_TX_LENGTH quirk" warning in many cases. Cc: <stable@vger.kernel.org> Reported-by: Eli Billauer <eli.billauer@gmail.com> Reported-by: Ard Biesheuvel <ardb@kernel.org> Tested-by: Eli Billauer <eli.billauer@gmail.com> Tested-by: Ard Biesheuvel <ardb@kernel.org> Signed-off-by: Mathias Nyman <mathias.nyman@linux.intel.com> Link: https://lore.kernel.org/r/20191211142007.8847-6-mathias.nyman@linux.intel.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions