diff options
| author | Ulf Hansson <ulf.hansson@linaro.org> | 2013-12-18 09:57:38 +0100 |
|---|---|---|
| committer | Chris Ball <chris@printf.net> | 2014-02-23 10:40:08 -0500 |
| commit | 68eb80e06bfa06035d0304686124974780308fae (patch) | |
| tree | 84a0dd60429c06284945edb365f568591464f3ab /drivers/mmc/host/sdhci.c | |
| parent | e18eaf8ff940d75d240d7dee6ab84363438f379e (diff) | |
| download | blackbird-op-linux-68eb80e06bfa06035d0304686124974780308fae.tar.gz blackbird-op-linux-68eb80e06bfa06035d0304686124974780308fae.zip | |
mmc: core: Rename max_discard_to to max_busy_timeout
Rename host->max_discard_to to host->max_busy_timeout, to reflect that
it tells the mmc core layer about the maximum supported busy detection
timeout by the host.
This timeout is at the moment only applicable to erase/trim/discard
commands. By the renaming we provide the option of make use of it for
other commands that cares about busy detection. In other words, those
commands that wants an R1B response, like for example the mmc switch
command.
Do note that the max_busy_timeout is supposed to be specified only by
hosts supporting MMC_CAP_WAIT_WHILE_BUSY.
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Signed-off-by: Chris Ball <chris@printf.net>
Diffstat (limited to 'drivers/mmc/host/sdhci.c')
| -rw-r--r-- | drivers/mmc/host/sdhci.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c index 8958edc03e04..d1e1bf52fe52 100644 --- a/drivers/mmc/host/sdhci.c +++ b/drivers/mmc/host/sdhci.c @@ -2941,7 +2941,7 @@ int sdhci_add_host(struct sdhci_host *host) if (host->quirks & SDHCI_QUIRK_DATA_TIMEOUT_USES_SDCLK) host->timeout_clk = mmc->f_max / 1000; - mmc->max_discard_to = (1 << 27) / host->timeout_clk; + mmc->max_busy_timeout = (1 << 27) / host->timeout_clk; mmc->caps |= MMC_CAP_SDIO_IRQ | MMC_CAP_ERASE | MMC_CAP_CMD23; |
