aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/mmc/host/meson-mx-sdio.c
diff options
context:
space:
mode:
authorUlf Hansson <ulf.hansson@linaro.org>2020-05-08 11:52:28 +0200
committerUlf Hansson <ulf.hansson@linaro.org>2020-05-28 11:22:14 +0200
commit04f2f45f410f4c1f591482afa1ab6a8c44f0b713 (patch)
treef6513694739348e570e2590fc54c2fdc11aa105f /drivers/mmc/host/meson-mx-sdio.c
parentmmc: sdricoh_cs: Throttle polling rate for commands (diff)
downloadlinux-dev-04f2f45f410f4c1f591482afa1ab6a8c44f0b713.tar.xz
linux-dev-04f2f45f410f4c1f591482afa1ab6a8c44f0b713.zip
mmc: sdricoh_cs: Respect the cmd->busy_timeout from the mmc core
Using a fixed 1s polling timeout for all commands 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) 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. Note that, even if the sdricoh_cs driver may currently not support HW busy detection on DAT0, some comments in the code refer to that the HW may support it. Therefore, it seems better to be proactive in this case. Cc: Sascha Sommer <saschasommer@freenet.de> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org> Link: https://lore.kernel.org/r/20200508095228.14230-1-ulf.hansson@linaro.org
Diffstat (limited to 'drivers/mmc/host/meson-mx-sdio.c')
0 files changed, 0 insertions, 0 deletions