From: Michal Pecio <michal.pecio@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: "Xuetao (kirin)" <xuetao09@huawei.com>, <caiyadong@huawei.com>,
<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v3 0/3] usb: wBytesPerInterval workaround and cleanups
Date: Mon, 18 May 2026 07:30:26 +0200 [thread overview]
Message-ID: <20260518073026.5580bb79.michal.pecio@gmail.com> (raw)
This series provides a workaround for certain devices with bogus
wBytesPerInterval field in interrupt endpoint descriptors and enables
them to work on the latest pedantic xHCI controllers.
It also fixes USB3 root hub descriptors and improves error logging.
new in v3:
all: add cover letter
rebase on 7.1 to fix context conflicts
1/1: reduce wMaxPacketSize instead of raising wBytesPerInterval,
as pointed out by Mathias Nyman
new in v2:
2/3: added reporter's tested-by
use usb_endpoint_is_int_in() as suggested by Alan
3/3: new patch
Michal Pecio (3):
usb: core: Fix SuperSpeed root hub wMaxPacketSize
usb: core: Fix up Interrupt IN endpoints with bogus wBytesPerInterval
usb: core: Clean up SuperSpeed/eUSB2 descriptor validation logging
drivers/usb/core/config.c | 46 ++++++++++++++++-----------------------
drivers/usb/core/hcd.c | 4 +---
2 files changed, 20 insertions(+), 30 deletions(-)
--
2.48.1
next reply other threads:[~2026-05-18 5:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 5:30 Michal Pecio [this message]
2026-05-18 5:31 ` [PATCH v3 1/3] usb: core: Fix SuperSpeed root hub wMaxPacketSize Michal Pecio
2026-05-18 5:32 ` [PATCH v3 2/3] usb: core: Fix up Interrupt IN endpoints with bogus wBytesPerInterval Michal Pecio
2026-05-18 5:32 ` [PATCH v3 3/3] usb: core: Clean up SuperSpeed/eUSB2 descriptor validation logging Michal Pecio
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=20260518073026.5580bb79.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=caiyadong@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=stern@rowland.harvard.edu \
--cc=xuetao09@huawei.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