From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Ladi Prosek <lprosek@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 7/9] usb-hub: set PORT_STAT_C_SUSPEND on host-initiated wake-up
Date: Mon, 29 May 2017 15:09:54 +0200 [thread overview]
Message-ID: <20170529130956.20297-8-kraxel@redhat.com> (raw)
In-Reply-To: <20170529130956.20297-1-kraxel@redhat.com>
From: Ladi Prosek <lprosek@redhat.com>
PORT_STAT_C_SUSPEND should be set even on host-initiated wake-up,
i.e. on ClearPortFeature(PORT_SUSPEND). Windows is known to not
work properly otherwise.
Side note, since PORT_ENABLE looks similar and might appear to
have the same issue: According to 11.24.2.7.2.2 C_PORT_ENABLE:
"This bit is set when the PORT_ENABLE bit changes from one to
zero as a result of a Port Error condition (see Section 11.8.1).
This bit is not set on any other changes to PORT_ENABLE."
Signed-off-by: Ladi Prosek <lprosek@redhat.com>
Message-id: 20170522123325.2199-1-lprosek@redhat.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
hw/usb/dev-hub.c | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/hw/usb/dev-hub.c b/hw/usb/dev-hub.c
index 47b7519910..e82a6a6c44 100644
--- a/hw/usb/dev-hub.c
+++ b/hw/usb/dev-hub.c
@@ -402,7 +402,20 @@ static void usb_hub_handle_control(USBDevice *dev, USBPacket *p,
port->wPortChange &= ~PORT_STAT_C_ENABLE;
break;
case PORT_SUSPEND:
- port->wPortStatus &= ~PORT_STAT_SUSPEND;
+ if (port->wPortStatus & PORT_STAT_SUSPEND) {
+ port->wPortStatus &= ~PORT_STAT_SUSPEND;
+
+ /*
+ * USB Spec rev2.0 11.24.2.7.2.3 C_PORT_SUSPEND
+ * "This bit is set on the following transitions:
+ * - On transition from the Resuming state to the
+ * SendEOP [sic] state"
+ *
+ * Note that this includes both remote wake-up and
+ * explicit ClearPortFeature(PORT_SUSPEND).
+ */
+ port->wPortChange |= PORT_STAT_C_SUSPEND;
+ }
break;
case PORT_C_SUSPEND:
port->wPortChange &= ~PORT_STAT_C_SUSPEND;
--
2.9.3
next prev parent reply other threads:[~2017-05-29 13:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 13:09 [Qemu-devel] [PULL 0/9] usb patch queue Gerd Hoffmann
2017-05-29 13:09 ` [Qemu-devel] [PULL 1/9] ehci: fix overflow in frame timer code Gerd Hoffmann
2017-05-29 13:09 ` [Qemu-devel] [PULL 2/9] usb: Deprecate the legacy -usbdevice option Gerd Hoffmann
2017-05-29 13:09 ` [Qemu-devel] [PULL 3/9] usb: Deprecate HMP commands usb_add and usb_del Gerd Hoffmann
2017-05-29 13:09 ` [Qemu-devel] [PULL 4/9] usb: Simplify the parameter parsing of the legacy usb serial device Gerd Hoffmann
2017-05-29 13:09 ` [Qemu-devel] [PULL 5/9] xhci: split into multiple files Gerd Hoffmann
2017-05-29 13:09 ` [Qemu-devel] [PULL 6/9] xhci: add CONFIG_USB_XHCI_NEC option Gerd Hoffmann
2017-05-29 13:09 ` Gerd Hoffmann [this message]
2017-05-29 13:09 ` [Qemu-devel] [PULL 8/9] usb: don't wakeup during coldplug Gerd Hoffmann
2017-05-29 13:09 ` [Qemu-devel] [PULL 9/9] ehci: fix frame timer invocation Gerd Hoffmann
2017-05-30 9:43 ` [Qemu-devel] [PULL 0/9] usb patch queue Stefan Hajnoczi
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=20170529130956.20297-8-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=lprosek@redhat.com \
--cc=qemu-devel@nongnu.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).