From mboxrd@z Thu Jan 1 00:00:00 1970 From: broonie@opensource.wolfsonmicro.com (Mark Brown) Date: Thu, 14 Jun 2012 13:12:34 +0100 Subject: Where to power on the wifi device before loading the driver. In-Reply-To: <20120614063120.GA20167@avionic-0098.mockup.avionic-design.de> References: <6B4D417B830BC44B8026029FD256F7F1C377BFFE88@HKMAIL01.nvidia.com> <4FD90352.9090606@wwwdotorg.org> <20120614063120.GA20167@avionic-0098.mockup.avionic-design.de> Message-ID: <20120614121234.GC3913@opensource.wolfsonmicro.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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: