diff options
| author | Doug Anderson <dianders@chromium.org> | 2014-04-22 16:51:21 -0700 |
|---|---|---|
| committer | Chris Ball <chris@printf.net> | 2014-05-22 08:33:31 -0400 |
| commit | e6cc0123d91e52a454d9e958b9124ca8a61fd82c (patch) | |
| tree | 418ce1763a2b67f1e115d8605a93dd4ac0562e85 /drivers | |
| parent | da91a8f9c0f56d75b35bfe2e2456187ab55b3639 (diff) | |
| download | linux-e6cc0123d91e52a454d9e958b9124ca8a61fd82c.tar.bz2 | |
mmc: dw_mmc: Don't print data errors
Data errors are completely expected during tuning. Printing them out
is confusing people looking at the kernel logs. They see things like:
[ 3.613296] dwmmc_exynos 12200000.dwmmc0: data error, status 0x00000088
...and they think something is wrong with their hardware.
Remove the printouts. We'll leave it up to a higher level to report
about errors.
Signed-off-by: Doug Anderson <dianders@chromium.org>
Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Signed-off-by: Chris Ball <chris@printf.net>
Diffstat (limited to 'drivers')
| -rw-r--r-- | drivers/mmc/host/dw_mmc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c index d40991299218..1ac227c603b7 100644 --- a/drivers/mmc/host/dw_mmc.c +++ b/drivers/mmc/host/dw_mmc.c @@ -1229,7 +1229,7 @@ static int dw_mci_data_complete(struct dw_mci *host, struct mmc_data *data) data->error = -EIO; } - dev_err(host->dev, "data error, status 0x%08x\n", status); + dev_dbg(host->dev, "data error, status 0x%08x\n", status); /* * After an error, there may be data lingering |