All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Andy Ross <andy.ross@windriver.com>
Cc: linux-mmc@vger.kernel.org, Hein Tibosch <hein_tibosch@yahoo.es>,
	Pierre Ossman <pierre@ossman.eu>,
	Ben Nizette <bn@niasdigital.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Adrian Hunter <adrian.hunter@nokia.com>,
	Matt Fleming <matt@console-pimps.org>
Subject: Re: [PATCH] Fix sd/sdio/mmc initialization frequency retries
Date: Tue, 4 Jan 2011 01:29:02 +0000	[thread overview]
Message-ID: <20110104012901.GA8788@void.printf.net> (raw)
In-Reply-To: <4D221748.5040701@windriver.com>

Hi Andy,

On Mon, Jan 03, 2011 at 10:36:56AM -0800, Andy Ross wrote:
> Subject: [PATCH] Fix sd/sdio/mmc initialization frequency retries
> 
> Rewrite and clean up mmc_rescan() to properly retry frequencies lower
> than 400kHz.  Failures can happen both in sd_send_* calls and
> mmc_attach_*.  Break out "mmc_rescan_try_freq" from the frequency
> selection loop.  Symmetrize claim/release logic in mmc_attach_* API,
> and move the sd_send_* calls there to make mmc_rescan easier to read.
> 
> Signed-off-by: Andy Ross <andy.ross@windriver.com>

Thanks!  Pushed to mmc-next for .38, after adding Reviewed-by: tags and
removing the mmc_bus_{put,get}() comment, since I'll take care of that
separately.

-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2011-01-04  1:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-28 17:15 [PATCH] Fix sd/sdio/mmc initialization frequency retries Andy Ross
2010-12-31  4:49 ` Chris Ball
2011-01-03 18:36   ` Andy Ross
2011-01-04  1:29     ` Chris Ball [this message]
2011-01-04 17:27       ` Chris Ball
2010-12-31 20:43 ` Hein_Tibosch
2011-01-02 18:08   ` Hein_Tibosch

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=20110104012901.GA8788@void.printf.net \
    --to=cjb@laptop.org \
    --cc=adrian.hunter@nokia.com \
    --cc=andy.ross@windriver.com \
    --cc=bn@niasdigital.com \
    --cc=hein_tibosch@yahoo.es \
    --cc=linux-mmc@vger.kernel.org \
    --cc=matt@console-pimps.org \
    --cc=pierre@ossman.eu \
    --cc=s.hauer@pengutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.