From: Adrian Hunter <adrian.hunter@intel.com>
To: Ritesh Harjani <riteshh@codeaurora.org>, ulf.hansson@linaro.org
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
shawn.lin@rock-chips.com, linux-arm-msm@vger.kernel.org,
georgi.djakov@linaro.org, asutoshd@codeaurora.org,
stummala@codeaurora.org, venkatg@codeaurora.org,
pramod.gurav@linaro.org, jeremymc@redhat.com
Subject: Re: [RESEND RFC 3/3] mmc: sdhci: Add more debug info in case of data error
Date: Thu, 19 Jan 2017 13:54:04 +0200 [thread overview]
Message-ID: <74840dea-18b6-3b51-67ae-e1ce3bb7fb58@intel.com> (raw)
In-Reply-To: <1484030515-16722-4-git-send-email-riteshh@codeaurora.org>
On 10/01/17 08:41, Ritesh Harjani wrote:
> print error log message and dump sdhc registers for debugging
> purpose in case of data errors (except when tuning commands
> generate CRC/timeout/end bit errors).
It is a bit ugly and probably only useful during driver development, so I am
not at all enthusiastic about this.
>
> Signed-off-by: Ritesh Harjani <riteshh@codeaurora.org>
> Signed-off-by: Asutosh Das <asutoshd@codeaurora.org>
> ---
> drivers/mmc/host/sdhci.c | 21 +++++++++++++++++++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mmc/host/sdhci.c b/drivers/mmc/host/sdhci.c
> index 73a8918..2e51e49 100644
> --- a/drivers/mmc/host/sdhci.c
> +++ b/drivers/mmc/host/sdhci.c
> @@ -2616,9 +2616,26 @@ static void sdhci_data_irq(struct sdhci_host *host, u32 intmask)
> host->ops->adma_workaround(host, intmask);
> }
>
> - if (host->data->error)
> + if (host->data->error) {
> + bool pr_msg = true;
> +
> + if (intmask & (SDHCI_INT_DATA_CRC | SDHCI_INT_DATA_TIMEOUT |
> + SDHCI_INT_DATA_END_BIT)) {
> + command = SDHCI_GET_CMD(sdhci_readw(host,
> + SDHCI_COMMAND));
> + if (command == MMC_SEND_TUNING_BLOCK_HS200 ||
> + command == MMC_SEND_TUNING_BLOCK)
> + pr_msg = false;
> + }
> + if (pr_msg) {
> + pr_err("%s: data txfr (0x%08x) error: %d\n",
> + mmc_hostname(host->mmc), intmask,
> + host->data->error);
> + sdhci_dumpregs(host);
> + }
> +
> sdhci_finish_data(host);
> - else {
> + } else {
> if (intmask & (SDHCI_INT_DATA_AVAIL | SDHCI_INT_SPACE_AVAIL))
> sdhci_transfer_pio(host);
>
>
next prev parent reply other threads:[~2017-01-19 12:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 6:41 [RESEND RFC 0/3] mmc: sdhci: sdhci-msm: Add more debug logs Ritesh Harjani
2017-01-10 6:41 ` [RESEND RFC 1/3] mmc: sdhci: Add platform_dumpregs callback support to sdhci_ops Ritesh Harjani
2017-01-10 9:15 ` Shawn Lin
2017-01-18 7:57 ` Ritesh Harjani
2017-01-19 10:43 ` Adrian Hunter
2017-01-20 5:59 ` Ritesh Harjani
2017-01-10 6:41 ` [RESEND RFC 2/3] mmc: sdhci-msm: Implement platform_dumpregs callback in sdhci-msm Ritesh Harjani
2017-01-19 10:55 ` Adrian Hunter
2017-01-20 5:54 ` Ritesh Harjani
2017-01-10 6:41 ` [RESEND RFC 3/3] mmc: sdhci: Add more debug info in case of data error Ritesh Harjani
2017-01-19 11:54 ` Adrian Hunter [this message]
2017-01-20 6:26 ` Ritesh Harjani
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=74840dea-18b6-3b51-67ae-e1ce3bb7fb58@intel.com \
--to=adrian.hunter@intel.com \
--cc=asutoshd@codeaurora.org \
--cc=georgi.djakov@linaro.org \
--cc=jeremymc@redhat.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=pramod.gurav@linaro.org \
--cc=riteshh@codeaurora.org \
--cc=shawn.lin@rock-chips.com \
--cc=stummala@codeaurora.org \
--cc=ulf.hansson@linaro.org \
--cc=venkatg@codeaurora.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