linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: linux-mmc <linux-mmc@vger.kernel.org>,
	Aaron Lu <aaron.lu@intel.com>, Philip Rakity <prakity@nvidia.com>,
	Girish K S <girish.shivananjappa@linaro.org>,
	Al Cooper <alcooperx@gmail.com>,
	Arend van Spriel <arend@broadcom.com>
Subject: Re: [PATCH V3 00/15] mmc: host: Add facility to support re-tuning
Date: Mon, 16 Mar 2015 16:00:43 +0200	[thread overview]
Message-ID: <5506E20B.4090706@intel.com> (raw)
In-Reply-To: <1425991390-4983-1-git-send-email-adrian.hunter@intel.com>

On 10/03/15 14:42, Adrian Hunter wrote:
> Hi
> 
> Here is V3 of some patches to move re-tuning support
> out of sdhci and into the core, and add support for HS400
> re-tuning.
> 
> Currently sdhci does re-tuning transparently by
> calling sdhci_execute_tuning() from its ->request()
> function.
> 
> The problem with HS400 re-tuning is that it must be
> done in HS200 mode. That means using switch commands
> and making ios changes. That means it potentially
> conflicts with other command sequences. The new
> re-tuning support accomodates that.

Ulf, ping?


  parent reply	other threads:[~2015-03-16 14:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 12:42 [PATCH V3 00/15] mmc: host: Add facility to support re-tuning Adrian Hunter
2015-03-10 12:42 ` [PATCH V3 01/15] " Adrian Hunter
2015-03-10 12:42 ` [PATCH V3 02/15] mmc: core: Disable re-tuning when card is no longer initialized Adrian Hunter
2015-03-10 12:42 ` [PATCH V3 03/15] mmc: core: Add support for re-tuning before each request Adrian Hunter
2015-03-10 12:42 ` [PATCH V3 04/15] mmc: core: Check re-tuning before retrying Adrian Hunter
2015-03-10 12:43 ` [PATCH V3 05/15] mmc: core: Hold re-tuning during switch commands Adrian Hunter
2015-03-10 12:43 ` [PATCH V3 06/15] mmc: core: Hold re-tuning during erase commands Adrian Hunter
2015-03-10 12:43 ` [PATCH V3 07/15] mmc: core: Hold re-tuning while bkops ongoing Adrian Hunter
2015-03-10 12:43 ` [PATCH V3 08/15] mmc: mmc: Comment that callers need to hold re-tuning if the card is put to sleep Adrian Hunter
2015-03-10 12:43 ` [PATCH V3 09/15] mmc: core: Separate out the mmc_switch status check so it can be re-used Adrian Hunter
2015-03-10 12:43 ` [PATCH V3 10/15] mmc: core: Add support for HS400 re-tuning Adrian Hunter
2015-03-10 12:43 ` [PATCH V3 11/15] mmc: sdhci: Change to new way of doing re-tuning Adrian Hunter
2015-03-10 12:43 ` [PATCH V3 12/15] mmc: sdhci: Flag re-tuning is needed on CRC or End-Bit errors Adrian Hunter
2015-03-10 12:43 ` [PATCH V3 13/15] mmc: block: Check re-tuning in the recovery path Adrian Hunter
2015-03-10 12:43 ` [PATCH V3 14/15] mmc: block: Retry errored data requests when re-tuning is needed Adrian Hunter
2015-03-10 12:43 ` [PATCH V3 15/15] mmc: core: Don't print reset warning if reset is not supported Adrian Hunter
2015-03-16 14:00 ` Adrian Hunter [this message]
2015-03-23  8:06   ` [PATCH V3 00/15] mmc: host: Add facility to support re-tuning Adrian Hunter

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=5506E20B.4090706@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=aaron.lu@intel.com \
    --cc=alcooperx@gmail.com \
    --cc=arend@broadcom.com \
    --cc=girish.shivananjappa@linaro.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=prakity@nvidia.com \
    --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).