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 3/4] usb: xhci: add XHCI_MISS_CA_EVENT quirk bit
Date: Fri, 23 Dec 2016 14:52:57 +0800 [thread overview]
Message-ID: <1482475978-18203-4-git-send-email-baolu.lu@linux.intel.com> (raw)
In-Reply-To: <1482475978-18203-1-git-send-email-baolu.lu@linux.intel.com>
Writing the CMD_RING_ABORT bit in xhci command register should
cause a command completion event with the command completion
code set to command ring stopped. However on some hosts, the
CMD_RING_RUNNING bit is correctly cleared but the completion
event is never sent.
Current xhci driver treats the behavior of "CMD_RING_RUNNING
bit is correctly cleared but the completion event is missed"
as a correct behavior for all hosts. This is different from
that defined in xhci spec. Refer to 4.6.1.2 in xhci spec.
This patch introduces a quirk bit for those quirky hardwares.
For normal hosts, if the command completion for abort command
ring misses, we shall assume that there are larger problems
with the host and assert HCRST.
Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
---
drivers/usb/host/xhci-ring.c | 17 +++++------------
drivers/usb/host/xhci.h | 6 ++++++
2 files changed, 11 insertions(+), 12 deletions(-)
diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
index 5935dce..6a23c37 100644
--- a/drivers/usb/host/xhci-ring.c
+++ b/drivers/usb/host/xhci-ring.c
@@ -345,25 +345,18 @@ static int xhci_abort_cmd_ring(struct xhci_hcd *xhci, unsigned long *flags)
* larger problems with the xHC and assert HCRST.
*/
temp_64 = xhci_read_64(xhci, &xhci->op_regs->cmd_ring);
- if (temp_64 & CMD_RING_RUNNING) {
+ if ((temp_64 & CMD_RING_RUNNING) ||
+ !(xhci->quirks & XHCI_MISS_CA_EVENT)) {
xhci_err(xhci,
"Stop command ring failed, maybe the host is dead\n");
xhci->xhc_state |= XHCI_STATE_DYING;
xhci_halt(xhci);
return -ESHUTDOWN;
}
-
- /*
- * Writing the CMD_RING_ABORT bit should cause a cmd
- * completion event, however on some hosts the bit is
- * correctly cleared but the completion event is never
- * sent.
- */
- xhci_warn(xhci, "No stop event for abort, ring start fail?\n");
- xhci_cleanup_command_queue(xhci);
- } else {
- xhci_handle_stopped_cmd_ring(xhci, xhci_next_queued_cmd(xhci));
}
+
+ xhci_handle_stopped_cmd_ring(xhci, xhci_next_queued_cmd(xhci));
+
return 0;
}
diff --git a/drivers/usb/host/xhci.h b/drivers/usb/host/xhci.h
index 09fe63f..c550bf0 100644
--- a/drivers/usb/host/xhci.h
+++ b/drivers/usb/host/xhci.h
@@ -1656,6 +1656,12 @@ struct xhci_hcd {
#define XHCI_SSIC_PORT_UNUSED (1 << 22)
#define XHCI_NO_64BIT_SUPPORT (1 << 23)
#define XHCI_MISSING_CAS (1 << 24)
+/*
+ * Writing the CMD_RING_ABORT bit should cause a cmd completion event,
+ * however on some host hw the CMD_RING_RUNNING bit is correctly cleared
+ * but the completion event is never sent.
+ */
+#define XHCI_MISS_CA_EVENT (1 << 25)
unsigned int num_active_eps;
unsigned int limit_active_eps;
/* There are two roothubs to keep track of bus suspend info for */
--
2.1.4
next prev parent 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 [PATCH 0/4] refactor command timeout handling Lu Baolu
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 ` Lu Baolu [this message]
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-4-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