On 01/13/2012 05:22 PM, Aaro Koskinen wrote:
Anyway, I think the change is good. On systems with multiple MMC devices the boot/probe can spend 100-200 ms alone just doing busylooping delays. I think e.g. in mmc_rescan() the code uses frequently mmc_delay(10).
I'm worrying about this: mmc_delay(DIV_ROUND_UP(card->ext_csd.sa_timeout, 10000)) since I have no ideas about typical values for this timeout. If it may be too small (<=10 us), using usleep_range() makes no sense. Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
