-
Ulf Hansson authored
The busy timeout that is computed for each erase/trim/discard operation, can become quite long and may thus exceed the host->max_busy_timeout. If that becomes the case, mmc_do_erase() converts from using an R1B response to an R1 response, as to prevent the host from doing HW busy detection. However, it has turned out that some hosts requires an R1B response no matter what, so let's respect that via checking MMC_CAP_NEED_RSP_BUSY. Note that, if the R1B gets enforced, the host becomes fully responsible of managing the needed busy timeout, in one way or the other. Suggested-by:
Sowjanya Komatineni <skomatineni@nvidia.com> Cc: <stable@vger.kernel.org> Tested-by:
Anders Roxell <anders.roxell@linaro.org> Tested-by:
Sowjanya Komatineni <skomatineni@nvidia.com> Tested-by:
Faiz Abbas <faiz_abbas@ti.com> Tested-By:
Peter Geis <pgwipeout@gmail.com> Signed-off-by:
Ulf Hansson <ulf.hansson@linaro.org>
43cc64e5