aboutsummaryrefslogtreecommitdiff
path: root/include/linux/debugobjects.h
diff options
context:
space:
mode:
authorUlf Hansson <[email protected]>2020-04-14 18:13:57 +0200
committerUlf Hansson <[email protected]>2020-05-28 11:21:00 +0200
commitef5053bdf5b64db714f3e8ee8fc9a6e37116365c (patch)
treef8faf33d163b6b1de58860788e10b6ad77bd2511 /include/linux/debugobjects.h
parentab5d94f73bcbbcd85959b4db948cc3d37255c23c (diff)
mmc: atmel-mci: Respect the cmd->busy_timeout from the mmc core
Using a fixed 2s timeout for all commands 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 2s. 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: Ludovic Desroches <[email protected]> Cc: Nicolas Ferre <[email protected]> Signed-off-by: Ulf Hansson <[email protected]> Acked-by: Ludovic Desroches <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Ulf Hansson <[email protected]>
Diffstat (limited to 'include/linux/debugobjects.h')
0 files changed, 0 insertions, 0 deletions