From: Chris Ball <cjb@laptop.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: "Torne \(Richard Coles\)" <torne@google.com>,
Ben Hutchings <ben@decadent.org.uk>,
linus.walleij@linaro.org, jh80.chung@samsung.com,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] MMC: core: cap MMC card timeouts at 2 seconds.
Date: Fri, 01 Jun 2012 10:48:14 -0400 [thread overview]
Message-ID: <87pq9jhyvl.fsf@laptop.org> (raw)
In-Reply-To: <4FC8BCA0.1000207@intel.com> (Adrian Hunter's message of "Fri, 01 Jun 2012 15:59:12 +0300")
Hi,
On Fri, Jun 01 2012, Adrian Hunter wrote:
> I just noticed that from linux 3.4, the SD write timeout is now 3 seconds
> triggering the sdhci driver warning on every write on every SD card.
> So change pr_warning to DGB in sdhci_calc_timeout(). Chris?
Oops, thanks for noticing:
Subject: mmc: sdhci: Use DBG() instead of pr_warning() on large timeout
3bdc9ba892d6 ("mmc: use really long write timeout to deal with crappy
cards") in 3.4 increased the write timeout that the core sends to host
drivers to 3 seconds. This makes sdhci's "requested timeout too large"
warning trigger on every write; so, change this pr_warning() to a DBG().
Reported-by: Adrian Hunter <adrian.hunter@intel.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
---
drivers/mmc/host/sdhci.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
index e626732..f4b8b4d 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 0x%x requested for CMD%d!\n",
- mmc_hostname(host->mmc), count, cmd->opcode);
+ DBG("%s: Too large timeout 0x%x requested for CMD%d!\n",
+ mmc_hostname(host->mmc), count, cmd->opcode);
count = 0xE;
}
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
prev parent reply other threads:[~2012-06-01 14:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 17:31 Torne (Richard Coles)
2012-05-29 2:32 ` Ben Hutchings
2012-05-29 9:02 ` Torne (Richard Coles)
2012-05-29 9:02 ` [PATCH] " Torne (Richard Coles)
2012-05-31 10:00 ` Ulf Hansson
2012-05-31 10:15 ` Torne (Richard Coles)
2012-05-31 15:00 ` Ulf Hansson
2012-06-01 8:35 ` [PATCH V2] " Adrian Hunter
2012-06-01 9:31 ` Torne (Richard Coles)
2012-06-01 9:32 ` Torne (Richard Coles)
2012-06-01 10:09 ` Adrian Hunter
2012-06-01 10:20 ` Torne (Richard Coles)
2012-06-01 12:59 ` Adrian Hunter
2012-06-01 13:12 ` Torne (Richard Coles)
2012-06-01 13:20 ` [PATCH V3] MMC: core: cap MMC card timeouts at UINT_MAX Torne (Richard Coles)
2012-06-04 8:13 ` Adrian Hunter
2012-06-01 14:48 ` Chris Ball [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pq9jhyvl.fsf@laptop.org \
--to=cjb@laptop.org \
--cc=adrian.hunter@intel.com \
--cc=ben@decadent.org.uk \
--cc=jh80.chung@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=torne@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome