From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: <gregkh@linuxfoundation.org>
Cc: <linux-usb@vger.kernel.org>,
Mathias Nyman <mathias.nyman@linux.intel.com>
Subject: [PATCH 0/2] xhci fixes for usb-linus
Date: Mon, 5 May 2025 15:56:28 +0300 [thread overview]
Message-ID: <20250505125630.561699-1-mathias.nyman@linux.intel.com> (raw)
Hi Greg
A couple xhci fixes for usb-linus.
Fix one DbC busyloop issue, and a VIA vendor specific issue.
The VIA issue is not marked for stable (yet) as it changes code
in the active path for all hosts.
A previous attempt at solving this caused regression, so letting
this get some real life exposure before adding it to stable.
Thanks
Mathias
Mathias Nyman (1):
xhci: dbc: Avoid event polling busyloop if pending rx transfers are
inactive.
Michal Pecio (1):
usb: xhci: Don't trust the EP Context cycle bit when moving HW dequeue
drivers/usb/host/xhci-dbgcap.c | 19 ++++++++++++++++---
drivers/usb/host/xhci-dbgcap.h | 3 +++
drivers/usb/host/xhci-ring.c | 19 +++++++++----------
3 files changed, 28 insertions(+), 13 deletions(-)
--
2.43.0
next reply other threads:[~2025-05-05 12:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 12:56 Mathias Nyman [this message]
2025-05-05 12:56 ` [PATCH 1/2] usb: xhci: Don't trust the EP Context cycle bit when moving HW dequeue Mathias Nyman
2025-05-05 12:56 ` [PATCH 2/2] xhci: dbc: Avoid event polling busyloop if pending rx transfers are inactive Mathias Nyman
-- strict thread matches above, loose matches on Subject: below --
2025-08-19 12:58 [PATCH 0/2] xhci fixes for usb-linus Mathias Nyman
2024-12-17 10:21 Mathias Nyman
2024-08-09 12:44 Mathias Nyman
2024-04-04 12:11 Mathias Nyman
2023-05-15 13:40 Mathias Nyman
2022-02-15 12:33 Mathias Nyman
2021-12-10 14:17 Mathias Nyman
2021-05-25 7:40 Mathias Nyman
2021-01-15 16:19 Mathias Nyman
2020-05-14 11:04 Mathias Nyman
2020-03-06 15:08 Mathias Nyman
2019-06-18 14:27 Mathias Nyman
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=20250505125630.561699-1-mathias.nyman@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).