From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Julius Werner <jwerner@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Vincent Palatin <vpalatin@chromium.org>,
Benson Leung <bleung@chromium.org>, Felipe Balbi <balbi@ti.com>,
mathias.nyman@linux.intel.com
Subject: Re: [PATCH] usb: xhci-plat: Enable USB 2.0 hardware LPM support for platform xHCs
Date: Wed, 21 Aug 2013 17:45:14 -0700 [thread overview]
Message-ID: <20130822004514.GB19747@xanatos> (raw)
In-Reply-To: <CAODwPW8tCFaykJnatyweJ96UzntRVNmo3WU1UYXw9nwp2bq_Ow@mail.gmail.com>
On Wed, Aug 21, 2013 at 02:43:55PM -0700, Julius Werner wrote:
> > Thanks for the patch! Did you test with a USB analyzer to see if the
> > device was actually going into USB 2.0 Link PM? I'd like to confirm we
> > really aren't breaking anything for DW3 hosts by enabling this.
>
> Yes, I did. The LPM transfers on the analyzer look good and the device
> works as expected.
Ok, good to know. Greg, is your USB tree still open for feature
requests? I wouldn't normally send you usb-next requests so late, but
this is pretty simple patch to extend a feature that's already in your
usb-next tree.
> My platform only runs a 3.8 derivative, though, so I now have also
> cherry-picked the BESL patches that went in since then to make sure
> they don't break things. I had problems on one device until I found
> the XHCI_BLC fix Mathias sent out this morning, so you should pick
> that one up first. (Without it LPM doesn't break completely but seems
> to assert resume for less time than the HIRD defines, so the device
> sometimes gets confused and resets. I can't figure out how BESL is
> really supposed to work since the XHCI spec from 8/14/12 where it's
> supposedly defined doesn't seem to be publicly available.)
You need the USB 2.0 spec errata from 2011-11 that describes the changes
made for BESL as well. It's in the USB2-LPM-Errata-final.pdf and
USB2_LinkPowerMangement_ECN[final].pdf files in this zip file:
http://www.usb.org/developers/docs/usb_20_070113.zip
I agree though, it's all a confusing mess for documentation on USB 2.0
Link PM.
Sarah Sharp
next prev parent reply other threads:[~2013-08-22 0:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 23:21 [PATCH] usb: xhci-plat: Enable USB 2.0 hardware LPM support for platform xHCs Julius Werner
2013-08-21 18:40 ` Sarah Sharp
2013-08-21 21:43 ` Julius Werner
2013-08-22 0:45 ` Sarah Sharp [this message]
2013-08-22 2:12 ` Greg Kroah-Hartman
2013-08-22 4:22 ` Julius Werner
2013-08-22 5:11 ` Paul Zimmerman
2013-08-26 19:14 ` Sarah Sharp
2013-08-26 19:37 ` Paul Zimmerman
2013-08-26 19:53 ` Paul Zimmerman
2013-08-28 21:51 ` Sarah Sharp
2013-08-28 22:15 ` Paul Zimmerman
2013-08-28 23:08 ` Julius Werner
2013-08-29 17:18 ` Sarah Sharp
2013-08-29 18:06 ` Julius Werner
2013-08-29 18:40 ` Paul Zimmerman
2013-11-06 20:33 ` Julius Werner
2013-12-02 21:50 ` Julius Werner
2013-08-29 17:42 ` Sarah Sharp
2013-08-29 18:11 ` Paul Zimmerman
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=20130822004514.GB19747@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=balbi@ti.com \
--cc=bleung@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=vpalatin@chromium.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