summaryrefslogtreecommitdiffstats
path: root/drivers/mmc/host/omap.c
diff options
context:
space:
mode:
authorDoug Anderson <dianders@chromium.org>2014-04-23 01:51:21 +0200
committerChris Ball <chris@printf.net>2014-05-22 14:33:31 +0200
commite6cc0123d91e52a454d9e958b9124ca8a61fd82c (patch)
tree418ce1763a2b67f1e115d8605a93dd4ac0562e85 /drivers/mmc/host/omap.c
parentmmc: sdhci: track whether preset mode is currently enabled in hardware (diff)
downloadlinux-e6cc0123d91e52a454d9e958b9124ca8a61fd82c.tar.xz
linux-e6cc0123d91e52a454d9e958b9124ca8a61fd82c.zip
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/mmc/host/omap.c')
0 files changed, 0 insertions, 0 deletions