aboutsummaryrefslogtreecommitdiff
path: root/include/linux/timerqueue.h
diff options
context:
space:
mode:
authorUlf Hansson <[email protected]>2020-04-14 18:14:10 +0200
committerUlf Hansson <[email protected]>2020-05-28 11:21:02 +0200
commit966244ccd2919e28f25555a77f204cd1c109cad8 (patch)
tree183d605e60af138b9f5912e2cb696cc5fbe9d4f7 /include/linux/timerqueue.h
parent0b05c9770501e949887abfe1c31c571e946eab64 (diff)
mmc: via-sdmmc: Respect the cmd->busy_timeout from the mmc core
Using a fixed 1s timeout for all commands (and data transfers) is a bit problematic. For some commands it means waiting longer than needed for the timer 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: Bruce Chang <[email protected]> Cc: Harald Welte <[email protected]> Signed-off-by: Ulf Hansson <[email protected]> Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'include/linux/timerqueue.h')
0 files changed, 0 insertions, 0 deletions