All of lore.kernel.org
 help / color / mirror / Atom feed
From: rtatiya@codeaurora.org
To: Oliver Neukum <oliver@neukum.org>
Cc: rtatiya@codeaurora.org, sarah.a.sharp@linux.intel.com,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] usb: Enable LPM for USB 2.01+ full-speed devices
Date: Wed, 8 Apr 2015 11:24:00 -0000	[thread overview]
Message-ID: <b201d47b7805afee4c9c4c4ba3e95372.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <1427272878.25161.4.camel@neukum.org>

>>
>> USB 2.01+ full-speed devices can have extended descriptor as well
>> and can support LPM.
>
> Yes, they in theory can, but what happens if they are actually
> asked to do so? On how many devices have you tested this patch?
>

I have tested this on Qualcomm USB controller, LPM works. LPM works with
same controller with Microsoft Windows as well. I have looked through few
Broadcom/CSR controllers, but could not find one that had USB version >=
2.01.

Thanks,
Rupesh

      reply	other threads:[~2015-04-08 11:24 UTC|newest]

Thread overview: 11+ 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:27       ` rtatiya
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-08 13:24           ` gpramod
2015-04-14 11:06       ` [PATCH v2] " Rupesh Tatiya
     [not found] ` <1427266399-19124-1-git-send-email-rtatiya-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2015-03-25  8:41   ` [PATCH] " Oliver Neukum
2015-03-25  8:41     ` Oliver Neukum
2015-04-08 11:24     ` rtatiya [this message]

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=b201d47b7805afee4c9c4c4ba3e95372.squirrel@www.codeaurora.org \
    --to=rtatiya@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.