aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHans Petter Selasky <hselasky@FreeBSD.org>2020-12-23 10:54:42 +0000
committerHans Petter Selasky <hselasky@FreeBSD.org>2020-12-23 11:04:51 +0000
commit1622a498525b4ef0d23d30a587b9a3888c3ee0d5 (patch)
treece402e4339308df4ef4169580f61b4318ade5527
parentddce63fcb6d0fe03a5f62fe819e04192c74f27c0 (diff)
downloadsrc-1622a498525b4ef0d23d30a587b9a3888c3ee0d5.tar.gz
src-1622a498525b4ef0d23d30a587b9a3888c3ee0d5.zip
No need to stop XHCI endpoints in disabled state.
Some AMD XHCI implementations apparently assert a permanent internal failure if this happens. Submitted by: ali.abdallah@suse.com PR: 251503 MFC after: 1 week Sponsored by: Mellanox Technologies // NVIDIA Networking
-rw-r--r--sys/dev/usb/controller/xhci.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/sys/dev/usb/controller/xhci.c b/sys/dev/usb/controller/xhci.c
index 1f8877546c27..10e37c97c254 100644
--- a/sys/dev/usb/controller/xhci.c
+++ b/sys/dev/usb/controller/xhci.c
@@ -3870,6 +3870,8 @@ xhci_configure_reset_endpoint(struct usb_xfer *xfer)
* endpoint context state diagram in the XHCI specification:
*/
switch (xhci_get_endpoint_state(udev, epno)) {
+ case XHCI_EPCTX_0_EPSTATE_DISABLED:
+ break;
case XHCI_EPCTX_0_EPSTATE_STOPPED:
break;
case XHCI_EPCTX_0_EPSTATE_HALTED: