public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michał Pecio" <michal.pecio@gmail.com>
To: chkr@plauener.de
Cc: linux-usb@vger.kernel.org
Subject: Re: Different speed of USB control transfers for HS USB devices depending on used USB port
Date: Mon, 9 Dec 2024 23:03:25 +0100	[thread overview]
Message-ID: <20241209230325.5a683364@foxbook> (raw)
In-Reply-To: <CAJugSwwpWKFbniGkdDCcGtKAbeYhoCsP=rMdmfaWGdFiFGEB0g@mail.gmail.com>

Hi,

I see obvious pattern that the bad ports are bus 001 and the good port
is bus 003, and they are two different chips.

Do you see similar correlation with chip types on other motherboards?

You can see the mapping between bus numbers and controllers using
ls -l /sys/bus/usb/devices/usb*

Generally, with xHCI it's on the controller to packetize and schedule 
such transfers, so this is likey a hardware problem.

Regards,
Michal

  reply	other threads:[~2024-12-09 22:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-09 18:19 Different speed of USB control transfers for HS USB devices depending on used USB port Christian Krause
2024-12-09 22:03 ` Michał Pecio [this message]
2024-12-10 17:18   ` Christian Krause

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=20241209230325.5a683364@foxbook \
    --to=michal.pecio@gmail.com \
    --cc=chkr@plauener.de \
    --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