On 06/14/2012 06:12 AM, Mark Brown wrote: > 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. Yes, that seems reasonable. Presumably the power GPIO should be a fixed regulator though, since it is a power control not just a plain old GPIO? That said, the current driver apparently deals with this as a GPIO already. The reset GPIO can separately/directly controlled by the WiFi driver though. -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
