From: Lu Baolu <baolu.lu@linux.intel.com>
To: Mathias Nyman <mathias.nyman@linux.intel.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: [PATCH 0/4] refactor command timeout handling
Date: Fri, 23 Dec 2016 14:52:54 +0800 [thread overview]
Message-ID: <1482475978-18203-1-git-send-email-baolu.lu@linux.intel.com> (raw)
Hi Mathias,
This patch series is for command timeout refactoring.
Patches
usb: xhci: remove unnecessary second abort try
usb: xhci: remove CRR polling in xhci_abort_cmd_ring()
are follow-ups of your comments of
"remove unnecessary second abort try as a separate patch, send to usb-next"
and
"remove polling for the Command ring running (CRR), waiting for completion
is enough, if completion times out then we can check CRR. for usb-next"
in below discussion thread.
https://lkml.org/lkml/2016/12/21/186
Patches
usb: xhci: add XHCI_MISS_CA_EVENT quirk bit
usb: xhci: warn on command timeout in stopped command ring
are my proposals.
They base on the top of your timeout_race_fixes branch.
(git://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git timeout_race_fixes)
Lu Baolu (4):
usb: xhci: remove unnecessary second abort try
usb: xhci: remove CRR polling in xhci_abort_cmd_ring()
usb: xhci: add XHCI_MISS_CA_EVENT quirk bit
usb: xhci: warn on command timeout in stopped command ring
drivers/usb/host/xhci-ring.c | 64 ++++++++++++++++++--------------------------
drivers/usb/host/xhci.h | 6 +++++
2 files changed, 32 insertions(+), 38 deletions(-)
--
2.1.4
next reply other threads:[~2016-12-23 6:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 6:52 Lu Baolu [this message]
2016-12-23 6:52 ` [PATCH 1/4] usb: xhci: remove unnecessary second abort try Lu Baolu
2016-12-23 6:52 ` [PATCH 2/4] usb: xhci: remove CRR polling in xhci_abort_cmd_ring() Lu Baolu
2016-12-23 6:52 ` [PATCH 3/4] usb: xhci: add XHCI_MISS_CA_EVENT quirk bit Lu Baolu
2016-12-23 6:52 ` [PATCH 4/4] usb: xhci: warn on command timeout in stopped command ring Lu Baolu
2016-12-23 9:49 ` Sergei Shtylyov
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=1482475978-18203-1-git-send-email-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.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
Powered by JetHome