From: Mark Brown <broonie@kernel.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Olof Johansson <olof@lixom.net>,
Alan Stern <stern@rowland.harvard.edu>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
Pawel Moll <Pawel.Moll@arm.com>,
Ian Campbell <ian.campbell@citrix.com>,
Felipe Balbi <balbi@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"devicetree@kernel.org" <devicetree@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Non-enumerable devices on USB and other enumerable buses
Date: Mon, 12 Aug 2013 21:38:03 +0100 [thread overview]
Message-ID: <20130812203803.GF6427@sirena.org.uk> (raw)
In-Reply-To: <52092491.7060605@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]
On Mon, Aug 12, 2013 at 12:08:17PM -0600, Stephen Warren wrote:
> In a similar way, I wonder if the USB case can be considered the same
> way? This seems less like a good fit since I don't expect the resources
> are always so similar there, and also there's the case of the bus being
> potentially behind a few levels of USB hub.
That won't work for the hub on Arndale in a system where it's fully
wired up - it's got an I2C interface for control and the idea is that
you bring it out of reset, write the configuration out via I2C and then
you can complete startup using a GPIO or another I2C command.
> And of course it all gets a little more messy when you get
> board-specific logic that needs setup, rather than something more common
> across multiple devices.
I think we could probably cover many cases by putting common things onto
the bus but we still need to confront the cases where the device driver
really does need to get involved in what's going on. Things like the
SDIO WiFi cards seem very interchangable as you say and would probably
benefit a lot but there's other applications that are less regular.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-12 20:38 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 [this message]
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=20130812203803.GF6427@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Pawel.Moll@arm.com \
--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=olof@lixom.net \
--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