From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Wei Ni <wni@nvidia.com>, 'Philip Rakity' <prakity@marvell.com>,
Rakesh Kumar <krakesh@nvidia.com>,
"'frankyl@broadcom.com'" <frankyl@broadcom.com>,
Thierry Reding <thierry.reding@avionic-design.de>,
Mursalin Akon <makon@nvidia.com>,
"'linux-mmc@vger.kernel.org'" <linux-mmc@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"'linux-wireless@vger.kernel.org'"
<linux-wireless@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: Where to power on the wifi device before loading the driver.
Date: Wed, 20 Jun 2012 11:47:44 +0100 [thread overview]
Message-ID: <20120620104744.GK3978@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FE112F2.7000506@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 825 bytes --]
On Tue, Jun 19, 2012 at 06:01:54PM -0600, Stephen Warren wrote:
> Unfortunately, it should be noted that the WiFi device socket on Cardhu
> apparently isn't some standardized thing (like PCIe) but something
> rather more custom, although there are apparently devices available to
> plug into it from multiple module vendors which contain WiFi chips from
> multiple chip vendors.
Right, and indeed someone may decide to plug in something that isn't a
WiFi device at all but some other SDIO attached device with totally
different uses for those GPIOs. Really these boards are an example of
the sort of thing I was talking about with modular reference systems,
though a simpler case as given what's brought out you probably can just
do something like list all the options that are there and allow hotplug
to sort things out.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-06-20 10:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 10:40 Where to power on the wifi device before loading the driver Wei Ni
2012-06-13 17:33 ` Franky Lin
2012-06-14 4:17 ` Wei Ni
2012-06-14 16:45 ` Franky Lin
2012-06-13 21:17 ` Stephen Warren
2012-06-14 6:31 ` Thierry Reding
2012-06-14 12:12 ` Mark Brown
2012-06-14 15:54 ` Stephen Warren
2012-06-15 6:09 ` Wei Ni
2012-06-15 15:49 ` Stephen Warren
2012-06-18 6:20 ` Wei Ni
2012-06-18 7:40 ` Rakesh Kumar
2012-06-18 8:03 ` Laxman Dewangan
2012-06-18 15:01 ` Stephen Warren
2012-06-19 9:13 ` Wei Ni
2012-06-19 1:23 ` Philip Rakity
2012-06-19 4:25 ` Wei Ni
2012-06-19 9:17 ` Mark Brown
2012-06-19 9:44 ` Wei Ni
2012-06-20 0:01 ` Stephen Warren
2012-06-20 10:47 ` Mark Brown [this message]
2012-06-20 11:28 ` Wei Ni
2012-06-20 16:51 ` Stephen Warren
2012-06-26 8:56 ` Dong Aisheng
2012-06-15 16:24 ` Franky Lin
2012-06-18 6:00 ` Wei Ni
2012-06-14 11:27 ` Wei Ni
2012-06-14 11:44 ` Wei Ni
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=20120620104744.GK3978@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=frankyl@broadcom.com \
--cc=grant.likely@secretlab.ca \
--cc=krakesh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=makon@nvidia.com \
--cc=prakity@marvell.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@avionic-design.de \
--cc=wni@nvidia.com \
/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).