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: Fri, 31 Dec 2010 04:49:42 +0000 [thread overview]
Message-ID: <20101231044942.GC19122@void.printf.net> (raw)
In-Reply-To: <4D1A1B19.8000902@windriver.com>
Hi Andy,
This patch doesn't apply against mmc-next, which makes it hard to review
properly; could you rebase/resend?
I like the look of these changes, just a few comments:
On Tue, Dec 28, 2010 at 09:15:05AM -0800, Andy Ross wrote:
> @@ -1450,19 +1440,12 @@ void mmc_rescan(struct work_struct *work)
> if ((host->bus_ops != NULL) && host->bus_ops->detect && !host->bus_dead)
> host->bus_ops->detect(host);
>
> - mmc_bus_put(host);
> -
> -
> - mmc_bus_get(host);
> -
> /* if there still is a card present, stop here */
> if (host->bus_ops != NULL) {
> mmc_bus_put(host);
> goto out;
> }
Let's leave these in -- I think we're depending on the side-effect of
mmc_bus_put() clearing out host->bus_ops. I'll check and submit a
separate patch adding a comment there explaining what's going on.
> + /* Try SDIO, then SD, then MMC */
> + if(mmc_attach_sdio(host) == 0)
> + break;
> + else if(mmc_attach_sd(host) == 0)
> + break;
> + else if(mmc_attach_mmc(host) == 0)
> + break;
Space after if, and perhaps let's use !mmc_attach_*() rather than == 0
for brevity. I guess we could also consider:
/* Try SDIO, then SD, then MMC */
if (mmc_attach_sdio(host) && mmc_attach_sd(host) &&
mmc_attach_mmc(host))
mmc_power_off(host);
mmc_release_host(host);
which would save quite a few lines, but perhaps it's less clear (or not
equivalent somehow). What do you think?
> -out_fail:
> - mmc_release_host(host);
> - mmc_power_off(host);
> + mmc_power_off(host);
This looks misaligned.
> + if((err = mmc_send_op_cond(host, 0, &ocr)))
> + return err;
Redundant parens, and space after if.
> + if((err =mmc_send_io_op_cond(host, 0, &ocr)))
As above, plus space after =.
Thanks! You might also consider splitting this up into two separate
patches, but I'll leave that up to you.
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2010-12-31 4:49 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 [this message]
2011-01-03 18:36 ` Andy Ross
2011-01-04 1:29 ` Chris Ball
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=20101231044942.GC19122@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 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).