From: Mark Brown <broonie@kernel.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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>,
Grant Likely <grant.likely@linaro.org>,
devicetree@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Non-enumerable devices on USB and other enumerable buses
Date: Wed, 14 Aug 2013 16:39:06 +0100 [thread overview]
Message-ID: <20130814153906.GU6427@sirena.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1308141023150.1701-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
On Wed, Aug 14, 2013 at 10:27:26AM -0400, Alan Stern wrote:
> On Wed, 14 Aug 2013, Mark Brown wrote:
> > I'd expect that we're just looking at hooks around connection and
> > disconnection here here - if we're looking at much more it seems like we
> > must be doing something wrong.
> Connection and disconnection of what?
The device on the bus.
> In the example mentioned earlier, the GPIOs to power an on-board USB
> hub would have to be initialized when the host controller was started.
> You wouldn't want to wait for the on-board hub to be detected, because
> without those GPIOs set properly, it never would be discovered on the
> USB bus. Right?
Yes, so you'd want callbacks when the device actually appears and
disappears.
> Perhaps the platform-level code would need to hook into the places
> where the discoverable bus is registered and unregistered.
We'd need some way to get information to the drivers still, and to
handle drivers that want to stop and start things.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-14 15:39 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
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 [this message]
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=20130814153906.GU6427@sirena.org.uk \
--to=broonie@kernel.org \
--cc=balbi@ti.com \
--cc=devicetree@vger.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