linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH v2 0/2] Fixes for command errors during tuning
Date: Wed, 6 Mar 2019 15:48:23 +0530	[thread overview]
Message-ID: <e5fb69c2-72a4-4b82-ea65-e0b314fdf28f@ti.com> (raw)
In-Reply-To: <20190301083824.23918-1-faiz_abbas@ti.com>

Hi,

On 01/03/19 2:08 PM, Faiz Abbas wrote:
> 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.
> 
> 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: Add platform_cmd_err() to sdhci_ops
>   mmc: sdhci-omap: Don't finish_mrq() on a command error during tuning
> 
>  drivers/mmc/host/sdhci-omap.c | 24 +++++++++++++++++++++
>  drivers/mmc/host/sdhci.c      | 40 +++++++++++++++++++++++------------
>  drivers/mmc/host/sdhci.h      |  4 ++++
>  3 files changed, 54 insertions(+), 14 deletions(-)
>

Gentle ping.

Thanks,
Faiz


      parent reply	other threads:[~2019-03-06 10:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-01  8:38 [PATCH v2 0/2] Fixes for command errors during tuning Faiz Abbas
2019-03-01  8:38 ` [PATCH v2 1/2] mmc: sdhci: Add platform_cmd_err() to sdhci_ops Faiz Abbas
2019-03-01  8:38 ` [PATCH v2 2/2] mmc: sdhci-omap: Don't finish_mrq() on a command error during tuning Faiz Abbas
2019-03-06 12:09   ` Adrian Hunter
2019-03-12 17:34     ` Rizvi, Mohammad Faiz Abbas
2019-03-13  9:35       ` Hunter, Adrian
2019-03-06 10:18 ` Faiz Abbas [this message]

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=e5fb69c2-72a4-4b82-ea65-e0b314fdf28f@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).