mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jens Glathe" <jens.glathe@oldschoolsolutions.biz>
To: mathias.nyman@intel.com
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH] fix: add XHCI_SPURIOUS_SUCCESS to ASM1042 despite being a V0.96 controller
Date: Tue, 30 Aug 2022 16:31:47 +0000	[thread overview]
Message-ID: <emc5c926da-851b-4152-8d2f-9d43bab7bcdc@607fe812.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 499 bytes --]

Hi there,

first try at a patch which was an actual pain with my Lenovo T500 
notebook, augmented with an USB3 PCMCIA card that has an ASM1042 chip. 
Inspired by this email thread: 
https://markmail.org/thread/7vzqbe7t6du6qsw3

ASM1042 identifies as a 0x96 XHCI host, brings spurious transfer event 
errors with a r8152 (Realtek 8153a) USB3 enthernet adapter. Additionally 
setting quirk XHCI_SPURIOUS_SUCCESS seems to resolve this issue in this 
case.

wiith best regards

Jens Glathe

[-- Attachment #2: 0001-fix-add-XHCI_SPURIOUS_SUCCESS-to-ASM1042-despite-bei.patch --]
[-- Type: text/plain, Size: 1421 bytes --]

From eac3410eeaf03c111add4dce247c4002fc58ba5d Mon Sep 17 00:00:00 2001
From: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Date: Sun, 28 Aug 2022 16:23:41 +0200
Subject: [PATCH] fix: add XHCI_SPURIOUS_SUCCESS to ASM1042 despite being a
 V0.96 controller

only if it reports as a V0.96 XHCI controller. Appears to fix the errors
"xhci_hcd <address>; ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13"
that appear spuriously (or pretty often) when using a r8152 USB3 ethernet adapter with integrated hub.
---
 drivers/usb/host/xhci-pci.c | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/drivers/usb/host/xhci-pci.c b/drivers/usb/host/xhci-pci.c
index dce6c0ec8d34..035229bc6d29 100644
--- a/drivers/usb/host/xhci-pci.c
+++ b/drivers/usb/host/xhci-pci.c
@@ -306,8 +306,14 @@ static void xhci_pci_quirks(struct device *dev, struct xhci_hcd *xhci)
 	}
 
 	if (pdev->vendor == PCI_VENDOR_ID_ASMEDIA &&
-		pdev->device == PCI_DEVICE_ID_ASMEDIA_1042_XHCI)
+		pdev->device == PCI_DEVICE_ID_ASMEDIA_1042_XHCI) {
+    /* try to tame the ASMedia 1042 controller which is 0.96 
+    */
+	  if (xhci->hci_version == 0x96) {
+      xhci->quirks |= XHCI_SPURIOUS_SUCCESS;
+    }
 		xhci->quirks |= XHCI_BROKEN_STREAMS;
+	}
 	if (pdev->vendor == PCI_VENDOR_ID_ASMEDIA &&
 		pdev->device == PCI_DEVICE_ID_ASMEDIA_1042A_XHCI) {
 		xhci->quirks |= XHCI_TRUST_TX_LENGTH;
-- 
2.25.1


             reply	other threads:[~2022-08-30 16:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 16:31 Jens Glathe [this message]
     [not found] <em007c3aa5-02c9-4a51-b789-6973e5f116ef@607fe812.com>
2022-08-30 16:32 ` Greg KH
     [not found] <20220830160035.10333-1-jens.glathe@oldschoolsolutions.biz>
2022-09-22 12:00 ` Greg KH
2022-09-25 17:22 Jens Glathe
2022-09-26  8:37 ` Greg KH
2022-09-26 11:31 ` Mathias Nyman
2022-09-26 15:18   ` Alan Stern

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=emc5c926da-851b-4152-8d2f-9d43bab7bcdc@607fe812.com \
    --to=jens.glathe@oldschoolsolutions.biz \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®