[...] >> The retry mechanism provided by mmc_wait_for_cmd() and friends really only >> makes sense for simple commands. In other cases, like this, we need to >> consider what state the card is in. For __mmc_switch we need to consider >> whether the card is busy or whether a timing change been made. > > I definitely agree. We should remove retries for CMD6 and perhaps also > for some other cases. > > When we have changed the above in __mmc_switch(), the change Chaotian > suggest gets a different impact, as it would potentially allow a > re-tuning to happen before the next CMD1to poll for busy or to check /s/CMD1/CMD13 > the switch status. This isn't okay. > > This all sounds to me that Chaotian's issue may not all be related to > tuning, but to the CMD6 switch sequence itself. However I may be wrong > - of course. :-) > > [...] > > Kind regards > Uffe -- 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
