From: Vyacheslav Vahnenko <vahnenko2003@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-usb@vger.kernel.org, vahnenko2003@gmail.com
Subject: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed
Date: Fri, 13 Mar 2026 15:36:38 +0300 [thread overview]
Message-ID: <20260313123638.20481-1-vahnenko2003@gmail.com> (raw)
In-Reply-To: <2026031332-askew-policy-c4ec@gregkh>
Add USB_QUIRK_NO_BOS for ezcap401 capture card, without it dmesg will show
"unable to get BOS descriptor or descriptor too short"
and "unable to read config index 0 descriptor/start: -71" errors
and device will not able to work at full speed at 10gbs
Signed-off-by: Vyacheslav Vahnenko <vahnenko2003@gmail.com>
---
drivers/usb/core/quirks.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
index 9e7e49712..0010f41a3 100644
--- a/drivers/usb/core/quirks.c
+++ b/drivers/usb/core/quirks.c
@@ -574,6 +574,9 @@ static const struct usb_device_id usb_quirk_list[] = {
/* Alcor Link AK9563 SC Reader used in 2022 Lenovo ThinkPads */
{ USB_DEVICE(0x2ce3, 0x9563), .driver_info = USB_QUIRK_NO_LPM },
+ /* ezcap401 - BOS descriptor fetch hangs at SuperSpeed Plus */
+ { USB_DEVICE(0x32ed, 0x0401), .driver_info = USB_QUIRK_NO_BOS },
+
/* DELL USB GEN2 */
{ USB_DEVICE(0x413c, 0xb062), .driver_info = USB_QUIRK_NO_LPM | USB_QUIRK_RESET_RESUME },
--
2.53.0
Thanks Greg for your patience, I'm not familiar with email stuff let alone kernel maintenance :)
Vyacheslav
next prev parent reply other threads:[~2026-03-13 12:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 18:10 ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed CaTaTo
2026-03-13 7:08 ` Greg KH
2026-03-13 9:54 ` CaTaTo
2026-03-13 10:11 ` Greg KH
2026-03-13 11:01 ` Vyacheslav Vahnenko
2026-03-13 12:04 ` Greg KH
2026-03-13 12:36 ` Vyacheslav Vahnenko [this message]
2026-03-13 17:20 ` ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed 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=20260313123638.20481-1-vahnenko2003@gmail.com \
--to=vahnenko2003@gmail.com \
--cc=gregkh@linuxfoundation.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.