diff options
| author | Mark Brown <broonie@opensource.wolfsonmicro.com> | 2012-04-10 10:36:03 (GMT) |
|---|---|---|
| committer | Chris Ball <cjb@laptop.org> | 2012-04-22 15:17:16 (GMT) |
| commit | 021459773d9b93e8d7388086db7b17107bdfc51d (patch) | |
| tree | e6736133f6790711f72491526ef397a1a5b26694 /drivers | |
| parent | 7f8bea7f75618165d015f083c77f1db3e4584f88 (diff) | |
| download | linux-021459773d9b93e8d7388086db7b17107bdfc51d.tar.xz | |
mmc: sdhci: Log what timeout was set if the timeout is too large
Rather than just logging that we came up with an excessively large timeout
say what the timeout was, this may provide some clues as to what the issue
is.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
Diffstat (limited to 'drivers')
| -rw-r--r-- | drivers/mmc/host/sdhci.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c index ccefdeb..e626732 100644 --- a/drivers/mmc/host/sdhci.c +++ b/drivers/mmc/host/sdhci.c @@ -680,8 +680,8 @@ static u8 sdhci_calc_timeout(struct sdhci_host *host, struct mmc_command *cmd) } if (count >= 0xF) { - pr_warning("%s: Too large timeout requested for CMD%d!\n", - mmc_hostname(host->mmc), cmd->opcode); + pr_warning("%s: Too large timeout 0x%x requested for CMD%d!\n", + mmc_hostname(host->mmc), count, cmd->opcode); count = 0xE; } |