linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rupesh Tatiya <rtatiya@codeaurora.org>
To: sarah.a.sharp@linux.intel.com, linux-usb@vger.kernel.org,
	gregkh@linuxfoundation.org, oliver@neukum.org
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Rupesh Tatiya <rtatiya@codeaurora.org>
Subject: [PATCH v2] usb: Enable LPM for USB 2.01+ full-speed devices
Date: Tue, 14 Apr 2015 16:36:55 +0530	[thread overview]
Message-ID: <1429009615-17354-1-git-send-email-rtatiya@codeaurora.org> (raw)
In-Reply-To: <6101704ff4dc2e95b67146ed26d01c9f.squirrel@www.codeaurora.org>

USB 2.01+ full-speed devices can have extended descriptor as well
and can support LPM.

Signed-off-by: Rupesh Tatiya <rtatiya@codeaurora.org>
---
 drivers/usb/core/hub.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
index 9ef2d2c..1ed7b5d 100644
--- a/drivers/usb/core/hub.c
+++ b/drivers/usb/core/hub.c
@@ -140,7 +140,7 @@ static int usb_device_supports_lpm(struct usb_device *udev)
 	/* USB 2.1 (and greater) devices indicate LPM support through
 	 * their USB 2.0 Extended Capabilities BOS descriptor.
 	 */
-	if (udev->speed == USB_SPEED_HIGH) {
+	if (udev->speed == USB_SPEED_HIGH || udev->speed == USB_SPEED_FULL) {
 		if (udev->bos->ext_cap &&
 			(USB_LPM_SUPPORT &
 			 le32_to_cpu(udev->bos->ext_cap->bmAttributes)))
-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, 
a Linux Foundation Collaborative Project

  parent reply	other threads:[~2015-04-14 11:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25  6:53 [PATCH] usb: Enable LPM for USB 2.01+ full-speed devices rtatiya
2015-03-25  6:58 ` Greg KH
     [not found]   ` <20150325065824.GA25520-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-04-08 11:27     ` rtatiya-sgV2jX0FEOL9JmXXK+q4OQ
2015-04-08 11:37       ` Greg KH
     [not found]       ` <6101704ff4dc2e95b67146ed26d01c9f.squirrel-mMfbam+mt9083fI46fginR2eb7JE58TQ@public.gmane.org>
2015-04-08 13:24         ` gpramod-sgV2jX0FEOL9JmXXK+q4OQ
2015-04-14 11:06       ` Rupesh Tatiya [this message]
     [not found] ` <1427266399-19124-1-git-send-email-rtatiya-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-03-25  8:41   ` Oliver Neukum
2015-04-08 11:24     ` rtatiya

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=1429009615-17354-1-git-send-email-rtatiya@codeaurora.org \
    --to=rtatiya@codeaurora.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oliver@neukum.org \
    --cc=sarah.a.sharp@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;
as well as URLs for NNTP newsgroup(s).