From: Gavin Guo <gavin.guo@canonical.com>
To: sarah.a.sharp@linux.intel.com, mathias.nyman@intel.com,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: yk@canonical.com, anthony.wong@canonical.com, gerald.yang@canonical.com
Subject: [PATCH 1/1] usb: Check if port status is equal to RxDetect
Date: Fri, 11 Jul 2014 14:22:36 +0800 [thread overview]
Message-ID: <1405059756-11983-2-git-send-email-gavin.guo@canonical.com> (raw)
In-Reply-To: <1405059756-11983-1-git-send-email-gavin.guo@canonical.com>
When using USB 3.0 pen drive with the [AMD] FCH USB XHCI Controller
[1022:7814], the second hotplugging will experience the USB 3.0 pen
drive is recognized as high-speed device. After bisecting the kernel,
I found the commit number 41e7e056cdc662f704fa9262e5c6e213b4ab45dd
(USB: Allow USB 3.0 ports to be disabled.) causes the bug. After doing
some experiments, the bug can be fixed by avoiding executing the function
hub_usb3_port_disable(). Because the port status with [AMD] FCH USB
XHCI Controlleris [1022:7814] is already in RxDetect
(I tried printing out the port status before setting to Disabled state),
it's reasonable to check the port status before really executing
hub_usb3_port_disable().
Fixes: 41e7e056cdc6 (USB: Allow USB 3.0 ports to be disabled.)
Signed-off-by: Gavin Guo <gavin.guo@canonical.com>
---
drivers/usb/core/hub.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
index 21b99b4..e02ab62 100644
--- a/drivers/usb/core/hub.c
+++ b/drivers/usb/core/hub.c
@@ -889,6 +889,25 @@ static int hub_usb3_port_disable(struct usb_hub *hub, int port1)
if (!hub_is_superspeed(hub->hdev))
return -EINVAL;
+ ret = hub_port_status(hub, port1, &portstatus, &portchange);
+ if (ret < 0)
+ return ret;
+
+ /*
+ * USB controller Advanced Micro Devices,
+ * Inc. [AMD] FCH USB XHCI Controller [1022:7814] will have spurious result
+ * making the following usb 3.0 device hotplugging route to the 2.0 root hub
+ * and recognized as high-speed device if we set the usb 3.0 port link state
+ * to Disabled. Since it's already in USB_SS_PORT_LS_RX_DETECT state, we
+ * check the state here to avoid the bug.
+ */
+ if ((portstatus & USB_PORT_STAT_LINK_STATE) ==
+ USB_SS_PORT_LS_RX_DETECT) {
+ dev_dbg(&hub->ports[port1 - 1]->dev,
+ "The link state is already in USB_SS_PORT_LS_RX_DETECT\n");
+ return ret;
+ }
+
ret = hub_set_port_link_state(hub, port1, USB_SS_PORT_LS_SS_DISABLED);
if (ret)
return ret;
--
2.0.0
next prev parent reply other threads:[~2014-07-11 6:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 6:22 [PATCH 0/1] Fixes to the USB 3.0 detection as 2.0 on AMD platform Gavin Guo
2014-07-11 6:22 ` Gavin Guo [this message]
2014-07-11 23:33 ` [PATCH 1/1] usb: Check if port status is equal to RxDetect Gavin Guo
2014-07-15 14:24 ` Alan Stern
2014-07-11 23:32 ` [PATCH 0/1] Fixes to the USB 3.0 detection as 2.0 on AMD platform Gavin Guo
2014-07-12 0:04 ` Greg KH
2014-07-12 0:28 ` Gavin Guo
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=1405059756-11983-2-git-send-email-gavin.guo@canonical.com \
--to=gavin.guo@canonical.com \
--cc=anthony.wong@canonical.com \
--cc=gerald.yang@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=sarah.a.sharp@linux.intel.com \
--cc=yk@canonical.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
all inboxes | Powered by JetHome®