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/3] xhci fixes for usb-linus
Date: Tue, 21 Apr 2020 17:08:19 +0300 [thread overview]
Message-ID: <20200421140822.28233-1-mathias.nyman@linux.intel.com> (raw)
Hi Greg
These xhci fixes for usb-linus sort out halted empty endpoint handling,
protocol stall handling, and overcurrent handling.
Theses issues have caused usb devices to appear as if they stop working
suddenly, failed to enumerate LS/FS devices behind HS hubs (seen on some
audio devices), and host from freezing in case of suspend on over-current.
-Mathias
Mathias Nyman (3):
xhci: Fix handling halted endpoint even if endpoint ring appears empty
xhci: prevent bus suspend if a roothub port detected a over-current
condition
xhci: Don't clear hub TT buffer on ep0 protocol stall
drivers/usb/host/xhci-hub.c | 9 +++++++
drivers/usb/host/xhci-ring.c | 46 +++++++++++++++++++++++++++++++-----
drivers/usb/host/xhci.c | 14 +++++------
drivers/usb/host/xhci.h | 5 ++--
4 files changed, 59 insertions(+), 15 deletions(-)
--
2.17.1
next reply other threads:[~2020-04-21 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 14:08 Mathias Nyman [this message]
2020-04-21 14:08 ` [PATCH 1/3] xhci: Fix handling halted endpoint even if endpoint ring appears empty Mathias Nyman
2020-04-22 13:27 ` Sasha Levin
2020-04-21 14:08 ` [PATCH 2/3] xhci: prevent bus suspend if a roothub port detected a over-current condition Mathias Nyman
2020-04-21 14:08 ` [PATCH 3/3] xhci: Don't clear hub TT buffer on ep0 protocol stall Mathias Nyman
-- strict thread matches above, loose matches on Subject: below --
2023-03-30 14:30 [PATCH 0/3] xhci fixes for usb-linus Mathias Nyman
2022-08-25 15:08 Mathias Nyman
2022-04-08 13:48 Mathias Nyman
2020-10-28 20:31 Mathias Nyman
2020-08-21 9:15 Mathias Nyman
2019-10-25 14:30 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=20200421140822.28233-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).