On Mon, Nov 1, 2010 at 4:22 PM, Arnd Hannemann <[email protected]> wrote: > It looks like this: > > r...@ap4evb:~# modprobe b43 > [ 36.023437] cfg80211: Calling CRDA to update world regulatory domain > [ 36.460937] sdio_bus_probe() > [ 36.468750] sdio_bus_probe() calling pm_runtime_get_sync() > [ 36.468750] mmc_power_restore_host() begin > [ 36.570312] mmc_sdio_power_restore() begin > [ 36.570312] mmc_sdio_init_card() > [ 36.578125] mmc_sdio_init_card() mmc_send_io_op_cond ret=-110
OK, thanks. CMD5 time outs. I suspect it's similar to what we have with the XO-1.5: despite software calling mmc_power_off/on, the hardware does not go through full power off/on cycle. >> The interesting part is actually what happens after sdio_bus_probe(), >> not before it. > > Actually nothing special happens after sdio_bus_probe() The actual failure happens after it (in mmc_sdio_init_card). > With your patch the problem goes away, thanks. Thank you for testing this, Ohad. -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
