blob: bae5352c08cad2c297b0f7f20f007ca1d8ff6ace [file] [log] [blame]
From cd0926d19581f70d537c52f0a4532374a90a05c9 Mon Sep 17 00:00:00 2001
From: Ulf Hansson <>
Date: Tue, 10 Mar 2020 14:43:00 +0100
Subject: [PATCH] mmc: core: Respect MMC_CAP_NEED_RSP_BUSY for
commit 43cc64e5221cc6741252b64bc4531dd1eefb733d upstream.
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 <>
Cc: <>
Tested-by: Anders Roxell <>
Tested-by: Sowjanya Komatineni <>
Tested-by: Faiz Abbas <>
Tested-By: Peter Geis <>
Signed-off-by: Ulf Hansson <>
Signed-off-by: Paul Gortmaker <>
diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
index 221127324709..6db0efde7429 100644
--- a/drivers/mmc/core/core.c
+++ b/drivers/mmc/core/core.c
@@ -1733,8 +1733,11 @@ static int mmc_do_erase(struct mmc_card *card, unsigned int from,
* the erase operation does not exceed the max_busy_timeout, we should
* use R1B response. Or we need to prevent the host from doing hw busy
* detection, which is done by converting to a R1 response instead.
+ * Note, some hosts requires R1B, which also means they are on their own
+ * when it comes to deal with the busy timeout.
- if (card->host->max_busy_timeout &&
+ if (!(card->host->caps & MMC_CAP_NEED_RSP_BUSY) &&
+ card->host->max_busy_timeout &&
busy_timeout > card->host->max_busy_timeout) {
cmd.flags = MMC_RSP_SPI_R1 | MMC_RSP_R1 | MMC_CMD_AC;
} else {