stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <gregkh@linuxfoundation.org>
To: balbi@ti.com, gregkh@linuxfoundation.org, mathias.nyman@linux.intel.com
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "usb: host: xhci: use new USB_RESUME_TIMEOUT" has been added to the 3.19-stable tree
Date: Sat, 02 May 2015 15:24:35 +0200	[thread overview]
Message-ID: <1430573075962@kroah.com> (raw)


This is a note to let you know that I've just added the patch titled

    usb: host: xhci: use new USB_RESUME_TIMEOUT

to the 3.19-stable tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     usb-host-xhci-use-new-usb_resume_timeout.patch
and it can be found in the queue-3.19 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.


>From b9e451885deb6262dbaf5cd14aa77d192d9ac759 Mon Sep 17 00:00:00 2001
From: Felipe Balbi <balbi@ti.com>
Date: Fri, 13 Feb 2015 14:39:13 -0600
Subject: usb: host: xhci: use new USB_RESUME_TIMEOUT

From: Felipe Balbi <balbi@ti.com>

commit b9e451885deb6262dbaf5cd14aa77d192d9ac759 upstream.

Make sure we're using the new macro, so our
resume signaling will always pass certification.

Acked-by: Mathias Nyman <mathias.nyman@linux.intel.com>
Signed-off-by: Felipe Balbi <balbi@ti.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

---
 drivers/usb/host/xhci-ring.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/drivers/usb/host/xhci-ring.c
+++ b/drivers/usb/host/xhci-ring.c
@@ -1574,7 +1574,7 @@ static void handle_port_status(struct xh
 		} else {
 			xhci_dbg(xhci, "resume HS port %d\n", port_id);
 			bus_state->resume_done[faked_port_index] = jiffies +
-				msecs_to_jiffies(20);
+				msecs_to_jiffies(USB_RESUME_TIMEOUT);
 			set_bit(faked_port_index, &bus_state->resuming_ports);
 			mod_timer(&hcd->rh_timer,
 				  bus_state->resume_done[faked_port_index]);


Patches currently in stable-queue which might be from balbi@ti.com are

queue-3.19/usb-host-xhci-use-new-usb_resume_timeout.patch
queue-3.19/usb-host-sl811-use-new-usb_resume_timeout.patch
queue-3.19/usb-musb-use-new-usb_resume_timeout.patch
queue-3.19/usb-define-a-generic-usb_resume_timeout-macro.patch
queue-3.19/usb-host-oxu210hp-use-new-usb_resume_timeout.patch
queue-3.19/usb-host-isp116x-use-new-usb_resume_timeout.patch
queue-3.19/usb-host-r8a66597-use-new-usb_resume_timeout.patch
queue-3.19/usb-musb-core-fix-tx-rx-endpoint-order.patch
queue-3.19/usb-core-hub-use-new-usb_resume_timeout.patch
queue-3.19/usb-host-fusbh200-use-new-usb_resume_timeout.patch
queue-3.19/usb-gadget-printer-enqueue-printer-s-response-for-setup-request.patch
queue-3.19/usb-host-ehci-use-new-usb_resume_timeout.patch
queue-3.19/usb-host-uhci-use-new-usb_resume_timeout.patch
queue-3.19/usb-host-fotg210-use-new-usb_resume_timeout.patch
queue-3.19/usb-phy-find-the-right-match-in-devm_usb_phy_match.patch

                 reply	other threads:[~2015-05-02 13:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1430573075962@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=balbi@ti.com \
    --cc=mathias.nyman@linux.intel.com \
    --cc=stable-commits@vger.kernel.org \
    --cc=stable@vger.kernel.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).