Linux USB
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: A1RM4X <A1RM4X@a1rm4x.com>
Cc: A1RM4X <dev@a1rm4x.com>,
	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 15:36:58 +0100	[thread overview]
Message-ID: <2026020421-rhyme-aspire-0a5c@gregkh> (raw)
In-Reply-To: <CACy+XB-Z26Bx2Zb4omoRq00L4tTAQxe4QWSQ1f=eFMryqb8Ksw@mail.gmail.com>

On Wed, Feb 04, 2026 at 09:25:18AM -0500, A1RM4X wrote:
> Hi,
> 
> Please find attached the new patch which fixes the structure of the commit.

Attached patches do not work :(

> Why? If the option is not being used, the speed limit will be limited
> to 5000M, which limits the capture capabilities of the device (4K30fps
> at 5000M versus the expected 4K60fps at 10000M).

Why does the device slow down like this?  Is it a bug in it?

> What happens in userspace?
> - without patch
> [ 5036.674972] usb 2-2: new SuperSpeed Plus Gen 2x1 USB device number
> 2 using xhci_hcd
> [ 5041.770595] usb 2-2: unable to get BOS descriptor or descriptor too short
> [ 5041.770605] usb 2-2: unable to read config index 0 descriptor/start: -19
> [ 5041.955592] usb 2-2: Device not responding to setup address.
> [ 5042.162588] usb 2-2: Device not responding to setup address.
> [ 5042.370246] usb 2-2: device not accepting address 3, error -71
> [ 5042.373859] usb usb2-port2: attempt power cycle
> [ 5043.691464] usb 2-2: new SuperSpeed USB device number 5 using xhci_hcd
> [ 5043.887185] usb 2-2: LPM exit latency is zeroed, disabling LPM.
> [ 5043.980556] usb 2-2: New USB device found, idVendor=2b89,
> idProduct=5871, bcdDevice= 0.00
> [ 5043.980561] usb 2-2: New USB device strings: Mfr=6, Product=7, SerialNumber=3
> [ 5043.980563] usb 2-2: Product: UGREEN 35871
> [ 5043.980564] usb 2-2: Manufacturer: UGREEN 35871
> [ 5043.980564] usb 2-2: SerialNumber: PRODUCT
> [ 5044.166844] hid-generic 0003:2B89:5871.0007: hiddev99,hidraw6: USB
> HID v1.11 Device [UGREEN 35871 UGREEN 35871] on
> usb-0000:0b:00.0-2/input4
> [ 5044.188946] videodev: Linux video capture interface: v2.00
> [ 5044.207601] uvcvideo 2-2:1.1: Unknown video format
> 30313050-0000-0010-8000-00aa00389b71
> [ 5044.207606] uvcvideo 2-2:1.0: Found UVC 1.00 device UGREEN 35871 (2b89:5871)
> [ 5044.242584] usbcore: registered new interface driver uvcvideo
> 
> /:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/5p, 20000M/x2
>     |__ Port 002: Dev 005, If 0, Class=Video, Driver=uvcvideo, 5000M
>     |__ Port 002: Dev 005, If 1, Class=Video, Driver=uvcvideo, 5000M
>     |__ Port 002: Dev 005, If 2, Class=Audio, Driver=snd-usb-audio, 5000M
>     |__ Port 002: Dev 005, If 3, Class=Audio, Driver=snd-usb-audio, 5000M
>     |__ Port 002: Dev 005, If 4, Class=Human Interface Device,
> Driver=usbhid, 5000M
> 
> 
> - with patch
> [   51.913978] usb 6-1: new SuperSpeed Plus Gen 2x1 USB device number
> 3 using xhci_hcd
> [   52.181717] usb 6-1: New USB device found, idVendor=2b89,
> idProduct=5871, bcdDevice= 0.00
> [   52.181721] usb 6-1: New USB device strings: Mfr=6, Product=7, SerialNumber=3
> [   52.181724] usb 6-1: Product: UGREEN 35871
> [   52.181726] usb 6-1: Manufacturer: UGREEN 35871
> [   52.181728] usb 6-1: SerialNumber: PRODUCT
> [   52.284659] uvcvideo 6-1:1.1: Unknown video format
> 30313050-0000-0010-8000-00aa00389b71
> [   52.284666] uvcvideo 6-1:1.0: Found UVC 1.00 device UGREEN 35871 (2b89:5871)
> [   52.475086] hid-generic 0003:2B89:5871.000A: hiddev100,hidraw6: USB
> HID v1.11 Device [UGREEN 35871 UGREEN 35871] on
> usb-0000:0e:00.3-1/input4
> 
> /:  Bus 006.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/4p, 10000M
>     |__ Port 001: Dev 003, If 0, Class=Video, Driver=uvcvideo, 10000M
>     |__ Port 001: Dev 003, If 1, Class=Video, Driver=uvcvideo, 10000M
>     |__ Port 001: Dev 003, If 2, Class=Audio, Driver=snd-usb-audio, 10000M
>     |__ Port 001: Dev 003, If 3, Class=Audio, Driver=snd-usb-audio, 10000M
>     |__ Port 001: Dev 003, If 4, Class=Human Interface Device,
> Driver=usbhid, 10000M
> 
> 
> If more debug tests are required, please let me know how to proceed.

If you run `lsusb -v` you will read the BOS values, and then look at the
kernel to see if it has issues after that.

> --------------------------------
> 
> Regarding the Signed‑off‑by line, I would like to use my public
> content‑creator alias rather than my personal identity. Could you
> advise how to do this while remaining compliant with the DCO?

Sorry, I can't do that as I do not know who this is.

greg k-h

  reply	other threads:[~2026-02-04 14:37 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
2026-02-04 14:25   ` A1RM4X
2026-02-04 14:36     ` Greg KH [this message]
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=2026020421-rhyme-aspire-0a5c@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=A1RM4X@a1rm4x.com \
    --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