On Tue, Apr 14, 2020 at 06:14:13PM +0200, Ulf Hansson wrote: > Using a fixed 1s timeout for all commands is a bit problematic. > > For some commands it means waiting longer than needed for the timeout to > expire, which may not a big issue, but still. For other commands, like for > an erase (CMD38) that uses a R1B response, may require longer timeouts than > 1s. In these cases, we may end up treating the command as it failed, while > it just needed some more time to complete successfully. > > Fix the problem by respecting the cmd->busy_timeout, which is provided by > the mmc core. > > Cc: Rui Miguel Silva <rmfrfs@xxxxxxxxx> > Cc: Johan Hovold <johan@xxxxxxxxxx> > Cc: Alex Elder <elder@xxxxxxxxxx> > Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> > Cc: greybus-dev@xxxxxxxxxxxxxxxx > Signed-off-by: Ulf Hansson <ulf.hansson@xxxxxxxxxx> Acked-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
