On Fri, Apr 8, 2011 at 3:22 AM, Andrei Warkentin <andreiw@xxxxxxxxxxxx> wrote: >> + >> + /* >> + * According to the SD specs, some commands require a delay after >> + * issuing the command. >> + */ >> + if (idata->ic.postsleep_us) >> + udelay(idata->ic.postsleep_us); >> + > > How long can this possibly be? Does usleep make any sense here? > Just to expand further on the question... is this a delay after a command (and it's data transfer, if any) has completely completed and the card is idle as far as the host driver can tell??? Or is the timeout while the card is busy (and holding down DAT)? I popped over to the ASSD simplified spec, and I can see interesting items like Protected_Memory_WR_TIME and WR_SEC_BUSY_TIME, and from the vague description I think that's the timeout going into data.timeout_ns for such transfers. Thanks, A -- 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
