From: Faiz Abbas <faiz_abbas@ti.com>
To: <linux-kernel@vger.kernel.org>, <linux-mmc@vger.kernel.org>,
<linux-omap@vger.kernel.org>
Cc: <ulf.hansson@linaro.org>, <kishon@ti.com>,
<adrian.hunter@intel.com>, <faiz_abbas@ti.com>
Subject: [PATCH v4 0/2] Fix command errors during tuning
Date: Tue, 26 Mar 2019 16:30:55 +0530 [thread overview]
Message-ID: <20190326110057.7055-1-faiz_abbas@ti.com> (raw)
These patches fix the following error message in dra7xx boards:
[4.833198] mmc1: Got data interrupt 0x00000002 even though no data
operation was in progress.
Tested with 100 times boot tests on dra71x-evm, dra72x-evm and
dra7xx-evm.
v4:
Fixed commit description for patch 1.
Added SDHCI_INT_TIMEOUT to CMD_ERR_MASK in patch 2.
v3:
Removed the command error specific callback and using the already
existing sdhci_irq callback instead. No measurable drop in performance.
v2:
Added EXPORT_SYMBOL_GPL for sdhci_cmd_err and sdhci_send_command to fix
errors when built as module.
Faiz Abbas (2):
mmc: sdhci: Export sdhci_finish_command()
mmc: sdhci-omap: Don't finish_mrq() on a command error during tuning
drivers/mmc/host/sdhci-omap.c | 37 +++++++++++++++++++++++++++++++++++
drivers/mmc/host/sdhci.c | 3 ++-
drivers/mmc/host/sdhci.h | 1 +
3 files changed, 40 insertions(+), 1 deletion(-)
--
2.19.2
next reply other threads:[~2019-03-26 11:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 11:00 Faiz Abbas [this message]
2019-03-26 11:00 ` [PATCH v4 1/2] mmc: sdhci: Export sdhci_finish_command() Faiz Abbas
2019-03-26 11:00 ` [PATCH v4 2/2] mmc: sdhci-omap: Don't finish_mrq() on a command error during tuning Faiz Abbas
2019-03-27 11:15 ` Adrian Hunter
2019-03-27 11:47 ` Faiz Abbas
2019-03-28 8:13 ` Adrian Hunter
2019-03-29 7:42 ` Faiz Abbas
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=20190326110057.7055-1-faiz_abbas@ti.com \
--to=faiz_abbas@ti.com \
--cc=adrian.hunter@intel.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=ulf.hansson@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).