All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217434] New: SuperSpeed+ speed reporting wrong from Asmedia ASM3242
Date: Fri, 12 May 2023 14:23:12 +0000	[thread overview]
Message-ID: <bug-217434-208809@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=217434

            Bug ID: 217434
           Summary: SuperSpeed+ speed reporting wrong from Asmedia ASM3242
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: USB
          Assignee: drivers_usb@kernel-bugs.kernel.org
          Reporter: james@ettle.org.uk
        Regression: No

I have a PCIe plugin card with an Asmedia ASM3242 controller, PCI ID 1b21:3242,
that supports a 20Gbps transfer rate. SuperSpeed+ devices do connect at 10 and
20Gbps where supported, but lsusb -t always reports that they are connected at
5Gbps.

The devices I've tested this with are:

 - 10Gbps USB hub
 - RTL9210B based NVME enclosure, 10Gbps
 - ASM236X based NVME enclosure, 20Gbps

I believe the NVME enclosures are connecting at the stated speeds from
observing their measured transfer rates (which would be impossible otherwise).

This issue has been discussed already on linux-usb:

[1] https://marc.info/?l=linux-usb&m=161527212127481&w=2

and later when I encountered it:

[2] https://marc.info/?l=linux-usb&m=168046080403282&w=2

I applied Thinh's patch from the discussion under [1] ('capture the device
speed
from sublink speed notification') to Linux 6.2.9 and it corrected the
behaviour, but as noted in [2] this was a test-of-concept patch and a proper
xHCI quirk is needed. Unfortunately this is somewhat beyond this reporter's
ability -- hence I've made this KBZ entry, mainly so the issue doesn't get
lost.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2023-05-12 14:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 14:23 bugzilla-daemon [this message]
2023-05-26 20:42 ` [Bug 217434] SuperSpeed+ speed reporting wrong from Asmedia ASM3242 bugzilla-daemon

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=bug-217434-208809@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.