From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Mehmet Ilhan Bayoglu <memobayoglu2007@gmail.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: quirks: add WINDOWS_CONFIG_REQ_SIZE for Razer BlackShark V3
Date: Fri, 20 Nov 2026 17:08:03 +0100 [thread overview]
Message-ID: <2026112051-smirk-omnivore-0d65@gregkh> (raw)
In-Reply-To: <20260831191345.43869-1-memobayoglu2007@gmail.com>
On Mon, Aug 31, 2026 at 03:13:45PM -0400, Mehmet Ilhan Bayoglu wrote:
> The Razer BlackShark V3 and V3 Pro wireless dongles fingerprint the
> USB host by its configuration-descriptor read pattern during
> enumeration. Unless they see a single full-length (wLength=255)
> request like Windows sends, they refuse to bring up the wireless
> telemetry relay and battery, charging and EQ state all read back as
> zero.
>
> USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE already implements exactly this
> behaviour, so just register it for the four BlackShark V3 PIDs:
>
> 0x0576 V3 Pro (wired USB-C)
> 0x0577 V3 Pro (2.4GHz dongle)
> 0x0579 V3 (wired USB-C)
> 0x057a V3 (2.4GHz dongle)
>
> Both the dongle and the wired transport enumerate the same firmware
> and need the quirk. Verified on 0x057a and 0x0577: with the quirk the
> vendor channel answers and battery/charging/EQ read correctly;
> without it every vendor GET returns zero.
>
> Tested-by: Mehmet Ilhan Bayoglu <memobayoglu2007@gmail.com>
> Signed-off-by: Mehmet Ilhan Bayoglu <memobayoglu2007@gmail.com>
> ---
> drivers/usb/core/quirks.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
> index b5b577f0b..9b5420be2 100644
> --- a/drivers/usb/core/quirks.c
> +++ b/drivers/usb/core/quirks.c
> @@ -502,6 +502,11 @@ static const struct usb_device_id usb_quirk_list[] = {
> USB_QUIRK_LINEAR_UFRAME_INTR_BINTERVAL },
> /* Razer - Razer Kiyo Pro Webcam */
> { USB_DEVICE(0x1532, 0x0e05), .driver_info = USB_QUIRK_NO_LPM },
> + /* Razer BlackShark V3 / V3 Pro - unlock wireless telemetry relay */
> + { USB_DEVICE(0x1532, 0x0576), .driver_info = USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE },
> + { USB_DEVICE(0x1532, 0x0577), .driver_info = USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE },
> + { USB_DEVICE(0x1532, 0x0579), .driver_info = USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE },
> + { USB_DEVICE(0x1532, 0x057a), .driver_info = USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE },
This is not in sorted order :(
next prev parent reply other threads:[~2026-11-20 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 19:13 Mehmet Ilhan Bayoglu
2026-11-20 16:08 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-31 19:12 Mehmet Ilhan Bayoglu
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=2026112051-smirk-omnivore-0d65@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=memobayoglu2007@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®