Re: [PATCH] USB: quirks: add USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE for GameSir G7 SE

[Greg Kroah-Hartman <gregkh@linuxfoundation.org>]

On Sun, Sep 27, 2026 at 06:54:01PM +0300, Ali via B4 Relay wrote:
> From: Ali <aliresool567@gmail.com>
> 
> The GameSir G7 SE wired controller first enumerates as 3537:10a0 and
> then re-enumerates in a mode it picks from how the host enumerated it.
> 
> When the configuration descriptor is fetched the Linux way, 9 bytes
> followed by the full 80, the controller disconnects about 1 ms after
> its string descriptors have been read, before SET_CONFIGURATION, and
> comes back as 3537:1082, a generic HID gamepad without force feedback.
> 
> When the configuration descriptor is fetched in one 255-byte request,
> as Windows does, it comes back as 3537:1010 in Xbox One (GIP) mode,
> which xpad already supports, including rumble.
> 
> Skipping the device qualifier requests (USB_QUIRK_DEVICE_QUALIFIER)
> makes no difference; the configuration descriptor request size alone
> decides the mode. Add USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE for the 10a0
> identity, as is already done for the ShanWan Wireless Gamepad.
> 
> Cc: stable@vger.kernel.org
> Assisted-by: claude-opus-5-5
> Signed-off-by: Ali <aliresool567@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