public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218943] No SuperSpeedPlus on AM4/5 Hubs
Date: Sat, 22 Jun 2024 00:28:38 +0000	[thread overview]
Message-ID: <bug-218943-208809-c9s7ZyVglz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218943-208809@https.bugzilla.kernel.org/>

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

--- Comment #33 from Thinh.Nguyen@synopsys.com ---
On Fri, Jun 21, 2024, bugzilla-daemon@kernel.org wrote:
>
> https://urldefense.com/v3/__https://bugzilla.kernel.org/show_bug.cgi?id=218943__;!!A4F2R9G_pg!fODPpvu8QMI1SH2NW38mJgNxScddtxlr7-FRbFln8qt4ISm6Ib7P6OXrtb1YRRyf5zD7koRGYGLNbyWW0Ts_xUuGkHNHpFhB$ 
> 
> --- Comment #32 from Jarrard (jarrard@proton.me) ---
> To conclude this bug report I have moved the OBS server to windows as a temp
> solution but would like to return it to Linux eventually. 
> 
> However for that to happen I think 10Gbps would need to be manually flagged
> on
> this vendor+device ID with some patch.  
> 
> I have tried the suggested PATCH set already and it allows the HUB to connect
> at 10Gbps but the device itself remains at 5Gbps so further patching would be
> need. I do not know how to do this.

So it's not AsMedia host? Regardless, if the patch allows the host to
see SuperSpeed Plus hub, then it confirms the host controller reported
the wrong port speed ID in its root port.

The patch gets the speed from device notification instead. The device
notification sublink speed should be propagated for devices under the
hub. The fact that you still see 5Gbps means there are other problems
either due to the host controller or the hub.

> 
> If anyone is able to help with a manual kernel patch to test other then the
> one
> in the comments here then I'm happy to test.
> 
> Thankyou.
> 

It'd be better for the vendor to provide the support and patches to
resolve this since they have the knowledge and the tools to debug their
hardware.

I can only provide clues for whoever needs to proceed further.

BR,
Thinh

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

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

  parent reply	other threads:[~2024-06-22  0:28 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-07  0:01 [Bug 218943] New: No SuperSpeedPlus on AM4/5 Hubs bugzilla-daemon
2024-06-07  0:04 ` [Bug 218943] " bugzilla-daemon
2024-06-07  0:14 ` bugzilla-daemon
2024-06-07  0:15 ` bugzilla-daemon
2024-06-07 11:17 ` bugzilla-daemon
2024-06-07 13:42 ` bugzilla-daemon
2024-06-08  1:35 ` bugzilla-daemon
2024-06-08  1:36 ` bugzilla-daemon
2024-06-08  1:41 ` bugzilla-daemon
2024-06-08  1:43 ` bugzilla-daemon
2024-06-11  5:02 ` bugzilla-daemon
2024-06-11  5:03 ` bugzilla-daemon
2024-06-11  8:25 ` bugzilla-daemon
2024-06-11  8:43 ` bugzilla-daemon
2024-06-11  8:59 ` bugzilla-daemon
2024-06-11  9:02 ` bugzilla-daemon
2024-06-11 14:10 ` bugzilla-daemon
2024-06-11 14:33 ` bugzilla-daemon
2024-06-11 14:53 ` bugzilla-daemon
2024-06-12 20:38 ` bugzilla-daemon
2024-06-13  0:43   ` Thinh Nguyen
2024-06-13  0:43 ` bugzilla-daemon
2024-06-13  0:50 ` bugzilla-daemon
2024-06-13 13:01 ` bugzilla-daemon
2024-06-14  4:20 ` bugzilla-daemon
2024-06-14  4:34 ` bugzilla-daemon
2024-06-15  4:08 ` bugzilla-daemon
2024-06-17  2:50 ` bugzilla-daemon
2024-06-17  4:42 ` bugzilla-daemon
2024-06-17  4:48 ` bugzilla-daemon
2024-06-17  5:27 ` bugzilla-daemon
2024-06-17  5:52 ` bugzilla-daemon
2024-06-17  5:55 ` bugzilla-daemon
2024-06-21  2:24 ` bugzilla-daemon
2024-06-22  0:28   ` Thinh Nguyen
2024-06-22  0:28 ` bugzilla-daemon [this message]
2024-06-22  2:36 ` 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-218943-208809-c9s7ZyVglz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox