On Fri, Jun 19, 2009 at 3:24 PM, Pierre Ossman<pierre@xxxxxxxxx> wrote: > I'm afraid I don't understand the problem. If you power up the card > before the MMC system has started, it should still properly find the > card and activate the wl12xx driver once things are in sync. Okay a little more background: This is with the out-of-tree Android msm_sdcc host driver. There are various implicit assumptions in module ordering. For example, one of the platform callbacks sets a "virtual card select" flag, and then tries to notify the MMC host via another callback to do mmc_detect_change(). But that code runs before the MMC driver is loaded so the callback isn't yet registered and no one gets the notification. The Android loads the TI wifi module whenever someone uses it and then unloads it afterwards, so the current use of the msm_wifi platform driver is always after MMC is running. And that's why the set_power() callbacks exist in the first place: they enable the phone to turn off the module via gpios, disconnect external oscillators, etc. when the person isn't actively using the wifi (i.e. module is unloaded). A separate platform driver could still manage all of that. (The above is just from my reading the source, San can correct any errors.) IOW, this particular issue isn't related to the core in-tree code, I was just describing why my first try failed. I believe you that it will work fine once the Android specifics are worked out. > Do you want me to merge it? It can go via the wireless tree if that's ok with you, since the SPI driver already lives there and this all needs to be rebased on Kalle Valo's latest changes anyway. It'd be nice to get msm_sdcc upstream though. -- Bob Copeland %% www.bobcopeland.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
