From: Mark Brown <broonie@kernel.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ian.campbell@citrix.com>,
Felipe Balbi <balbi@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Grant Likely <grant.likely@linaro.org>,
devicetree@kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Non-enumerable devices on USB and other enumerable buses
Date: Mon, 12 Aug 2013 10:51:36 +0100 [thread overview]
Message-ID: <20130812095136.GJ6427@sirena.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1308112146410.29546-100000@netrider.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 1836 bytes --]
On Sun, Aug 11, 2013 at 09:53:01PM -0400, Alan Stern wrote:
> On Sun, 11 Aug 2013, Mark Brown wrote:
> > One example that's bugging me right now is that on the Insignal Arndale
> > platform there's a USB hub connected to one of the USB ports on the SoC
> > (not as a PHY, it seems we also need the internal PHY running to talk to
> > the device). The hub needs to be "plugged" into the SoC after the SoC
> > USB controller has started with some GPIOs so we need to tell the system
> > that the hub exists and needs to be synchronised with the USB controller.
> On the surface, this seems like a particularly simple case. Why wait
> until the SoC's USB controller has started? Why not "plug in" the hub
> via the GPIOs right from the beginning?
I tried that, it doesn't seem to work - for some reason it seems that
the hub is only successfully enumerated if it starts after its parent is
running. I don't know enough about USB to speculate on why that might
be, the GPIOs are brining the device out of reset not applying power or
anything.
> > Another case that's going to be problematic once it's in mainline is
> > Slimbus - this is a bus used in some embedded audio subsystems which is
> > enumerable in a similar manner to USB but where the devices on the bus
> > are normally powered up only on demand (causing them to hotplug when
> > used and unplug when idle) and have at least interrupt lines wired to
> > the SoC using a normal interrupt outside the enumerable bus.
> That is indeed more difficult, because it requires geniune cooperation
> between the bus and platform subsystems.
Yeah. You might want to do the same with for example a USB network
controller when you're in flight only mode, that seems to be one of the
more common reasons for doing this sort of thing with USB.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-12 9:52 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 19:08 Non-enumerable devices on USB and other enumerable buses Mark Brown
2013-08-11 22:08 ` Grant Likely
2013-08-12 14:41 ` Mark Brown
2013-08-12 1:53 ` Alan Stern
2013-08-12 9:51 ` Mark Brown [this message]
2013-08-12 11:07 ` Mark Rutland
2013-08-12 11:32 ` Mark Brown
2013-08-12 18:08 ` Stephen Warren
2013-08-12 20:38 ` Mark Brown
2013-08-12 2:02 ` Greg Kroah-Hartman
2013-08-12 11:23 ` Mark Brown
2013-08-12 20:50 ` Greg Kroah-Hartman
2013-08-12 21:40 ` Mark Brown
2013-08-13 1:04 ` Alan Stern
2013-08-14 11:38 ` Mark Brown
2013-08-14 14:27 ` Alan Stern
2013-08-14 15:39 ` Mark Brown
2013-08-14 16:14 ` Alan Stern
2013-08-14 16:30 ` Stephen Warren
2013-08-14 18:49 ` Mark Brown
2013-08-14 17:30 ` Mark Brown
2013-08-14 18:35 ` Alan Stern
2013-08-14 18:46 ` Mark Brown
2013-08-14 19:39 ` Alan Stern
2013-08-14 20:16 ` Paul Zimmerman
2013-08-14 23:59 ` Mark Brown
2013-08-14 23:55 ` Mark Brown
2013-08-15 14:42 ` Alan Stern
2013-08-15 17:10 ` Mark Brown
2013-08-15 17:55 ` Alan Stern
2013-08-15 19:32 ` Mark Brown
2013-08-15 20:42 ` Alan Stern
2013-08-15 22:54 ` Mark Brown
2013-08-16 14:42 ` Alan Stern
2013-08-16 18:39 ` Mark Brown
2013-08-16 19:27 ` Alan Stern
2013-08-16 20:00 ` Mark Brown
2013-08-16 20:39 ` Alan Stern
2013-08-16 22:46 ` Mark Brown
2013-08-17 1:29 ` Alan Stern
2013-08-19 12:17 ` Ming Lei
2013-08-19 16:01 ` Mark Brown
2013-08-20 13:19 ` Ming Lei
2013-08-20 15:02 ` Mark Brown
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=20130812095136.GJ6427@sirena.org.uk \
--to=broonie@kernel.org \
--cc=balbi@ti.com \
--cc=devicetree@kernel.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=ian.campbell@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=stern@rowland.harvard.edu \
--cc=swarren@wwwdotorg.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