From: balbi@ti.com (Felipe Balbi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] gpio-vbus: support disabling D+ pullup on suspend
Date: Wed, 22 Jun 2011 18:19:03 +0300 [thread overview]
Message-ID: <20110622151902.GN27654@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1106221055030.1977-100000@iolanthe.rowland.org>
Hi,
On Wed, Jun 22, 2011 at 11:02:27AM -0400, Alan Stern wrote:
> On Wed, 22 Jun 2011, Felipe Balbi wrote:
>
> > > In fact, something like this is _necessary_ for all UDC/PHY drivers
> > > unless the device can guarantee that it will automatically wake up from
> > > suspend in time to service a USB packet (note that the window for
> > > responding to a packet is only a few microseconds). Otherwise the
> > > device would appear to the host to be unresponsive and broken -- better
> > > to do a clean disconnect.
> > >
> > > If suspending the device while it is in use would cause problems ...
> > > then don't suspend it when it is in use!
> >
> > I second your thoughts, but today we don't have enough infrastructure to
> > communicate between PHY and Link, so a clean solution isn't possible,
> > right ?
> >
> > Should we block this patch due to that ?
>
> No, the patch is appropriate.
>
> We don't need better communication. If g_mass_storage (for example)
> knows that the device is in use, it can block suspends by returning
> -EBUSY from its own suspend callback. The UDC driver doesn't need to
> worry about these matters; it should assume that such things have
> already been handled elsewhere. That's what Dmitry meant when he was
> talking about a "higher level driver" -- maybe "lower level" would have
> been a better choice of words. :-)
>
> Until recently, ordering of the suspend callbacks didn't present any
> problem. The gadget device was a child of the UDC device and therefore
> its suspend callback would always be invoked first.
>
> With the new UDC framework, I don't know if this is true any more.
> It's something to consider.
it's still true, but with one extra device in the middle. e.g.:
musb is parent to udc-core which is parent to g_zero.
--
balbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20110622/4af441b7/attachment.sig>
next prev parent reply other threads:[~2011-06-22 15:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 12:20 [PATCH 1/2] gpio-vbus: support disabling D+ pullup on suspend Dmitry Eremin-Solenikov
2011-06-22 12:20 ` [PATCH 2/2] mioa701: move gpio-pullup functionality to gpio-vbus Dmitry Eremin-Solenikov
2011-06-22 12:40 ` Dmitry Eremin-Solenikov
2011-06-22 13:23 ` [PATCH 1/2] gpio-vbus: support disabling D+ pullup on suspend Felipe Balbi
2011-06-22 13:52 ` Dmitry Eremin-Solenikov
2011-06-22 14:01 ` Felipe Balbi
2011-06-22 14:15 ` Dmitry Eremin-Solenikov
2011-06-22 14:20 ` Felipe Balbi
2011-06-22 14:26 ` Dmitry Eremin-Solenikov
2011-06-22 14:30 ` Felipe Balbi
2011-06-22 14:30 ` Alan Stern
2011-06-22 14:32 ` Felipe Balbi
2011-06-22 15:02 ` Alan Stern
2011-06-22 15:19 ` Felipe Balbi [this message]
2011-06-25 9:26 ` Robert Jarzmik
2011-06-25 10:33 ` Dmitry Eremin-Solenikov
2011-06-25 12:02 ` Alan Stern
2011-06-27 20:39 ` Robert Jarzmik
2011-06-28 2:41 ` Peter Chen
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=20110622151902.GN27654@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=linux-arm-kernel@lists.infradead.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).