summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorUlf Hansson <ulf.hansson@linaro.org>2020-04-14 18:14:12 +0200
committerUlf Hansson <ulf.hansson@linaro.org>2020-05-28 11:21:02 +0200
commit5671ad667ebbe5e2aef77a89c775e9623b6bf4b8 (patch)
treeea46bf0e3cc64884967a1c8408032b0392b92412 /scripts
parent78a67b9224ade6da7d2d83c23a9858cb4dfcd64a (diff)
downloadcachepc-linux-5671ad667ebbe5e2aef77a89c775e9623b6bf4b8.tar.gz
cachepc-linux-5671ad667ebbe5e2aef77a89c775e9623b6bf4b8.zip
mmc: mmc_spi: Respect the cmd->busy_timeout from the mmc core
Using a fixed 3s polling timeout for all commands with R1B responses is a bit problematic. For some commands it means waiting longer than needed for the polling to be aborted, which may not a big issue, but still. For other commands, like for an erase (CMD38), may require longer timeouts than 3s. 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: Jonathan Neuschäfer <j.neuschaefer@gmx.net> Cc: Linus Walleij <linus.walleij@linaro.org> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Link: https://lore.kernel.org/r/20200414161413.3036-19-ulf.hansson@linaro.org
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions