From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: ZeroNinEX <zwq939681378@gmail.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: core: quirks: Skip device qualifier for BEITONG BTP-PG01A
Date: Mon, 26 Oct 2026 15:33:16 +0100 [thread overview]
Message-ID: <2026102603-diligence-handwoven-ecba@gregkh> (raw)
In-Reply-To: <20261026133448.10185-1-zwq939681378@gmail.com>
On Mon, Oct 26, 2026 at 09:34:48PM +0800, ZeroNinEX wrote:
> The BEITONG BTP-PG01A wireless controller dongle initially enumerates as
> 4131:800c. Device qualifier requests fail with -EPIPE, followed by
> failures to read the configuration descriptor. After port recovery,
> the dongle can enumerate as 045e:028e with only two interfaces, leaving
> the vendor configuration software unusable in a Windows guest.
>
> Add USB_QUIRK_DEVICE_QUALIFIER for 4131:800c to skip device qualifier
> requests. The dongle then enumerates as 20bc:5162 with five interfaces,
> including three HID interfaces, and the vendor software works through
> USB passthrough to a Windows VM.
>
> Tested both usbcore.quirks=4131:800c:i and the built-in entry on an xHCI
> host. The patched kernel was tested without a dynamic usbcore.quirks
> entry. The configuration-request size quirk alone did not resolve the
> enumeration failure.
>
> Signed-off-by: ZeroNinEX <zwq939681378@gmail.com>
Hi,
This is the friendly patch-bot of Greg Kroah-Hartman. You have sent him
a patch that has triggered this response. He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created. Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.
You are receiving this message because of the following common error(s)
as indicated below:
- It looks like you did not use your "real" name for the patch on either
the Signed-off-by: line, or the From: line (both of which have to
match). Please read the kernel file,
Documentation/process/submitting-patches.rst for how to do this
correctly.
If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.
thanks,
greg k-h's patch email bot
prev parent reply other threads:[~2026-10-26 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 13:34 ZeroNinEX
2026-10-26 14:33 ` Greg Kroah-Hartman [this message]
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=2026102603-diligence-handwoven-ecba@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=zwq939681378@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
all inboxes | Powered by JetHome®