From: Nikhil Solanke <nikhilsolanke5@gmail.com>
To: linux-usb@vger.kernel.org
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
stern@rowland.harvard.edu, michal.pecio@gmail.com,
corbet@lwn.net, skhan@linuxfoundation.org,
stable@vger.kernel.org, linux-doc@vger.kernel.org,
Nikhil Solanke <nikhilsolanke5@gmail.com>
Subject: [PATCH v4 0/2] usb: core: Add quirk for 255-byte initial config read
Date: Tue, 28 Jul 2026 01:24:32 +0530 [thread overview]
Message-ID: <20260727195434.14626-1-nikhilsolanke5@gmail.com> (raw)
This series adds a quirk for USB devices that fail enumeration when
the initial GET_DESCRIPTOR(CONFIGURATION) request uses wLength=9.
Patch 1 adds USB_QUIRK_WINDOWS_CONFIG_REQ_SIZE which causes
usb_get_configuration() to use wLength=255 for the initial config
descriptor request, mirroring long-standing Windows behavior.
Patch 2 splits announce_device() to log device identity before
enumeration, improving failure diagnosis.
Nikhil Solanke (2):
usb: core: Add quirk for 255-bytes initial config read
usb: hub: Split announce_device() to log device identity before
enumeration
Changes in v4:
- Reworded comments and messages
- Moved the memcpy() block that skips the second read after USB_QUIRK_DELAY_INIT
.../admin-guide/kernel-parameters.txt | 5 +++
drivers/usb/core/config.c | 32 ++++++++++++++-----
drivers/usb/core/hub.c | 16 +++++++---
drivers/usb/core/quirks.c | 4 +++
include/linux/usb/quirks.h | 3 ++
5 files changed, 48 insertions(+), 12 deletions(-)
--
2.54.0
next reply other threads:[~2026-07-27 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 19:54 Nikhil Solanke [this message]
2026-07-27 19:54 ` [PATCH v4 1/2] usb: core: Add quirk for 255-bytes initial config read Nikhil Solanke
2026-07-27 19:54 ` [PATCH v4 2/2] usb: hub: Split announce_device() to log device identity before enumeration Nikhil Solanke
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=20260727195434.14626-1-nikhilsolanke5@gmail.com \
--to=nikhilsolanke5@gmail.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michal.pecio@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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