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: Tue, 19 Jun 2012 10:17:19 +0100	[thread overview]
Message-ID: <20120619091719.GZ3974@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <6B4D417B830BC44B8026029FD256F7F1C6EE2DD622@HKMAIL01.nvidia.com>

On Tue, Jun 19, 2012 at 12:25:58PM +0800, Wei Ni wrote:

As Stephen previously said please fix your mail formatting - word
wrapping within paragraphs is important!

> On Tue, Jun 19, 2012 at 09:23:35, Philip Rakity wrote:
> >Why can't you use the regulator notify to get called back on power or 
> >voltage change options to plumb in the manipulation of the gpio. I can 
> >imagine you might need to add a notify call in core.c if you need to 
> >assert the gpio before power is applied
> 
> Yes, we can use the regulator notify, but the Tegra30 support is via
> device tree, I think there have no special board file to run the call
> back.

You can mix board files with device tree for cases where device tree is
not yet up to the job, though the goal should be to come up with a way
of expressing things in device tree.
-------------- 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/20120619/738ceb54/attachment.sig>

  reply	other threads:[~2012-06-19  9:17 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
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 [this message]
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=20120619091719.GZ3974@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).