From: Greg KH <gregkh@linuxfoundation.org>
To: A1RM4X <dev@a1rm4x.com>
Cc: linux-usb@vger.kernel.org, limiao@kylinos.cn, oneukum@suse.com,
huanglei@kylinos.cn, lijiayi@kylinos.cn,
johannes.bruederl@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: add QUIRK_NO_BOS for several devices
Date: Wed, 4 Feb 2026 06:15:09 +0100 [thread overview]
Message-ID: <2026020457-distrust-vision-e5de@gregkh> (raw)
In-Reply-To: <20260204032938.61553-1-dev@a1rm4x.com>
On Tue, Feb 03, 2026 at 10:29:38PM -0500, A1RM4X wrote:
> Add QUIRK_NO_BOS entries for:
> * ASUS TUF 4K PRO (0x0b05:0x1ab9)
> * Avermedia Live Gamer Ultra 2.1 (0x07ca:0x2553)
> * UGREEN 35871 (0x2b89:0x5871)
Why? What is the results without this option being used here? And what
happens when userspace goes and asks for this descriptor?
> Signed-off-by: A1RM4X <dev@a1rm4x.com>
We need a real name, sorry.
> ---
> drivers/usb/core/quirks.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
> index c4d85089d19b..ddce45ce9f6c 100644
> --- a/drivers/usb/core/quirks.c
> +++ b/drivers/usb/core/quirks.c
> @@ -453,6 +453,15 @@ static const struct usb_device_id usb_quirk_list[] = {
> /* Elgato 4K X - BOS descriptor fetch hangs at SuperSpeed Plus */
> { USB_DEVICE(0x0fd9, 0x009b), .driver_info = USB_QUIRK_NO_BOS },
>
> + /* ASUS TUF 4K PRO - BOS descriptor fetch hangs at SuperSpeed Plus */
> + { USB_DEVICE(0x0b05, 0x1ab9), .driver_info = USB_QUIRK_NO_BOS },
> +
> + /* Avermedia Live Gamer Ultra 2.1 (GC553G2) - BOS descriptor fetch hangs at SuperSpeed Plus */
> + { USB_DEVICE(0x07ca, 0x2553), .driver_info = USB_QUIRK_NO_BOS },
> +
> + /* UGREEN 35871 - BOS descriptor fetch hangs at SuperSpeed Plus */
> + { USB_DEVICE(0x2b89, 0x5871), .driver_info = USB_QUIRK_NO_BOS },
Please read the comment for this structure for how to place these in the
list.
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-04 5:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 3:29 [PATCH] usb: add QUIRK_NO_BOS for several devices A1RM4X
2026-02-04 5:15 ` Greg KH [this message]
2026-02-04 14:25 ` A1RM4X
2026-02-04 14:36 ` Greg KH
2026-02-04 14:37 ` Greg KH
2026-02-04 19:51 ` A1RM4X
2026-02-05 6:51 ` Greg KH
2026-02-05 17:24 ` sharms
2026-02-05 17:33 ` Greg KH
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=2026020457-distrust-vision-e5de@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dev@a1rm4x.com \
--cc=huanglei@kylinos.cn \
--cc=johannes.bruederl@gmail.com \
--cc=lijiayi@kylinos.cn \
--cc=limiao@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.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