aboutsummaryrefslogtreecommitdiff
path: root/include/linux/start_kernel.h
diff options
context:
space:
mode:
authorUlf Hansson <[email protected]>2020-04-14 18:14:13 +0200
committerUlf Hansson <[email protected]>2020-05-28 11:21:00 +0200
commita389087ee9f195fcf2f31cd771e9ec5f02c16650 (patch)
tree8e8c53df682e62e1fca030ea32495166bf59507b /include/linux/start_kernel.h
parent4c2e04d728046d693fa1ef60ca38aedd382bc0e3 (diff)
staging: greybus: sdio: Respect the cmd->busy_timeout from the mmc core
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 <[email protected]> Cc: Johan Hovold <[email protected]> Cc: Alex Elder <[email protected]> Cc: Greg Kroah-Hartman <[email protected]> Cc: [email protected] Signed-off-by: Ulf Hansson <[email protected]> Acked-by: Rui Miguel Silva <[email protected]> Acked-by: Greg Kroah-Hartman <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Ulf Hansson <[email protected]>
Diffstat (limited to 'include/linux/start_kernel.h')
0 files changed, 0 insertions, 0 deletions