Return-path: Received: from hqemgate04.nvidia.com ([216.228.121.35]:6740 "EHLO hqemgate04.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751245Ab2FSJoJ convert rfc822-to-8bit (ORCPT ); Tue, 19 Jun 2012 05:44:09 -0400 From: Wei Ni To: 'Mark Brown' CC: 'Philip Rakity' , 'Stephen Warren' , Rakesh Kumar , "'frankyl@broadcom.com'" , Thierry Reding , Mursalin Akon , "'linux-mmc@vger.kernel.org'" , "devicetree-discuss@lists.ozlabs.org" , "'linux-wireless@vger.kernel.org'" , "linux-tegra@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Date: Tue, 19 Jun 2012 17:44:00 +0800 Subject: RE: Where to power on the wifi device before loading the driver. Message-ID: <6B4D417B830BC44B8026029FD256F7F1C6EE2DD626@HKMAIL01.nvidia.com> (sfid-20120619_114414_640696_8B55F070) References: <6B4D417B830BC44B8026029FD256F7F1C377BFFE88@HKMAIL01.nvidia.com> <4FD90352.9090606@wwwdotorg.org> <20120614063120.GA20167@avionic-0098.mockup.avionic-design.de> <20120614121234.GC3913@opensource.wolfsonmicro.com> <4FDA092E.10301@wwwdotorg.org> <6B4D417B830BC44B8026029FD256F7F1C377BFFE8D@HKMAIL01.nvidia.com> <4FDB5976.20809@wwwdotorg.org> <6B4D417B830BC44B8026029FD256F7F1C6EE2DD61F@HKMAIL01.nvidia.com> <43E4817426ED174AA81263BCECB4351D138E8ACD6B@sc-vexch3.marvell.com> <6B4D417B830BC44B8026029FD256F7F1C6EE2DD622@HKMAIL01.nvidia.com> <20120619091719.GZ3974@opensource.wolfsonmicro.com> In-Reply-To: <20120619091719.GZ3974@opensource.wolfsonmicro.com> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Sender: linux-wireless-owner@vger.kernel.org List-ID: On Tue, Jun 19, 2012 at 17:17:19, Mark Brown wrote: >* PGP Signed by an unknown key > >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. I think we wish to use the device tree to handle these gpios, pass them to the related driver to assert them. If we mix the board files, we even can set these gpio directly, not use the notify. But I think this is not a goog way. Wei. --- nvpublic > >* Unknown Key >* 0x6E30FDDD