linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Where to power on the wifi device before loading the driver.
Date: Thu, 14 Jun 2012 13:12:34 +0100	[thread overview]
Message-ID: <20120614121234.GC3913@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120614063120.GA20167@avionic-0098.mockup.avionic-design.de>

On Thu, Jun 14, 2012 at 08:31:20AM +0200, Thierry Reding wrote:
> On Wed, Jun 13, 2012 at 03:17:06PM -0600, Stephen Warren wrote:

> > The core of the issue is that:

> > * Tegra30 support is via device tree.
> > * We have an SDIO bus, and the WiFi device attached to that bus is
> > enumerable.
> > * Since the WiFi device is enumerable, no node exists in the DT to
> > represent it.
> > * However, the driver for the WiFi device needs certain information,
> > such as the reset GPIO ID and perhaps power GPIO.

> PCI devices are also enumerable and yet they can be matched up with nodes in
> the device tree. Perhaps something similar could be added for the SDIO bus?

This seems to make the most sense - pushing this through the regulator
API is just a bodge.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120614/b30854cc/attachment.sig>

  reply	other threads:[~2012-06-14 12:12 UTC|newest]

Thread overview: 33+ 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 [this message]
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
2012-06-20 11:28                         ` Wei Ni
2012-06-20 16:51                           ` Stephen Warren
2012-06-26  8:56                         ` Dong Aisheng
2012-06-26 16:53                           ` Stephen Warren
2012-06-26 21:26                             ` Rob Herring
2012-06-26 22:38                               ` Stephen Warren
2012-06-27  2:19                               ` Dong Aisheng
2012-06-27  2:16                             ` 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=20120614121234.GC3913@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.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).