From: Greg KH <gregkh@linuxfoundation.org>
To: Vyacheslav Vahnenko <vahnenko2003@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re:
Date: Fri, 13 Mar 2026 13:04:42 +0100 [thread overview]
Message-ID: <2026031332-askew-policy-c4ec@gregkh> (raw)
In-Reply-To: <20260313110141.26264-1-vahnenko2003@gmail.com>
On Fri, Mar 13, 2026 at 02:01:41PM +0300, Vyacheslav Vahnenko wrote:
> 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
>
> Subject: ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed
Close, this should actually be the subject line, you forgot to have one
entirely in your email :)
And can you wrap the changelog text at 72 columns, like your editor
should have asked you to when making this change? If you run your patch
through scripts/checkpatch.pl before sending it, it should tell you
about these types of things.
> 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 },
This looks good, thanks for putting it in the right place.
Almost there!
greg k-h
next prev parent reply other threads:[~2026-03-13 12:04 UTC|newest]
Thread overview: 14+ 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 [this message]
2026-03-13 12:36 ` ezcap401 needs USB_QUIRK_NO_BOS to function on 10gbs usb speed Vyacheslav Vahnenko
2026-03-13 17:20 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2023-03-12 6:52 [PATCH v2] uas: Add US_FL_NO_REPORT_OPCODES for JMicron JMS583Gen 2 Greg Kroah-Hartman
2023-03-27 13:54 ` Yaroslav Furman
2023-03-27 14:19 ` Greg Kroah-Hartman
2021-12-20 6:46 Ralf Beck
2021-12-20 7:55 ` Greg KH
2021-12-20 10:01 ` Re: Oliver Neukum
[not found] <CAPXXXSDVGeEK_NCSkDMwTpuvVxYkWGdQk=L=bz+RN4XLiGZmcg@mail.gmail.com>
[not found] ` <CAPXXXSBYcU1QamovmP-gVTXms67Xi_QpMCV=V3570q1nnuWqNw@mail.gmail.com>
2020-04-04 21:05 ` Re: Ruslan Bilovol
2020-04-05 1:27 ` Re: Alan Stern
[not found] ` <CAPXXXSBLHYdHNSS4aM2Ax07+GQSB1WbPziOrk0iVWf-LXLmQRg@mail.gmail.com>
[not found] ` <CAPXXXSAajets4AqcBKt8aRd8V1AL4bjAmCyuBOKr8qBG-AHO1A@mail.gmail.com>
2020-04-05 2:51 ` Re: Colin Williams
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=2026031332-askew-policy-c4ec@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=vahnenko2003@gmail.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