diff options
author | Faiz Abbas <faiz_abbas@ti.com> | 2019-04-11 11:59:37 +0300 |
---|---|---|
committer | Ulf Hansson <ulf.hansson@linaro.org> | 2019-04-11 13:40:32 +0300 |
commit | 5c41ea6d52003b5bc77c2a82fd5ca7d480237d89 (patch) | |
tree | 728ed8df779df5c676d2e5308379ee50c6119935 /drivers/dax | |
parent | 157c99c5a2956a9ab1ae12de0136a2d8a1b1a307 (diff) | |
download | linux-5c41ea6d52003b5bc77c2a82fd5ca7d480237d89.tar.xz |
mmc: sdhci-omap: Don't finish_mrq() on a command error during tuning
commit 5b0d62108b46 ("mmc: sdhci-omap: Add platform specific reset
callback") skips data resets during tuning operation. Because of this,
a data error or data finish interrupt might still arrive after a command
error has been handled and the mrq ended. This ends up with a "mmc0: Got
data interrupt 0x00000002 even though no data operation was in progress"
error message.
Fix this by adding a platform specific callback for sdhci_irq. Mark the
mrq as a failure but wait for a data interrupt instead of calling
finish_mrq().
Fixes: 5b0d62108b46 ("mmc: sdhci-omap: Add platform specific reset
callback")
Signed-off-by: Faiz Abbas <faiz_abbas@ti.com>
Acked-by: Adrian Hunter <adrian.hunter@intel.com>
Cc: stable@vger.kernel.org
Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'drivers/dax')
0 files changed, 0 insertions, 0 deletions