public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: stummala@codeaurora.org
To: Michal Miroslaw <mirq-linux@rere.qmqm.pl>
Cc: Hein_Tibosch <hein_tibosch@yahoo.es>,
	Sahitya Tummala <stummala@codeaurora.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Pierre Ossman <pierre@ossman.eu>, Chris Ball <cjb@laptop.org>,
	Ben Nizette <bn@niasdigital.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Adrian Hunter <adrian.hunter@nokia.com>,
	linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Matt Fleming <matt@console-pimps.org>
Subject: Re: [PATCH v4] mmc: Make ID freq configurable
Date: Thu, 2 Dec 2010 21:05:54 -0800 (PST)	[thread overview]
Message-ID: <1c6eadd860e1a9085336bf75a2a96eb3.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <20101202223812.GA2685@rere.qmqm.pl>

Hi Michal,

> On Fri, Dec 03, 2010 at 05:21:10AM +0800, Hein_Tibosch wrote:
>> Hi Sahitya,
>> On 2-12-2010 19:16, Sahitya Tummala wrote:
>> > Hi Hein Tibosch,
>> >
>> > On Fri, 2010-09-03 at 05:34 +0800, Hein_Tibosch wrote:
>> >> In the latest releases of the mmc driver, the freq during
>> initialization
>> >> is set to a fixed 400 Khz. This was reportedly too fast for several
>> >> users. As there doesn't seem to be an ideal frequency
>> which-works-for-all,
>> >> Pierre suggested to let the driver try several frequencies.
>> >> <cut>
>> >> +		/*
>> >> +		 * First we search for SDIO...
>> >> +		 */
>> >> +		err = mmc_send_io_op_cond(host, 0, &ocr);
>> >> +		if (!err) {
>> >> +			if (mmc_attach_sdio(host, ocr)) {
>> >> +				mmc_claim_host(host);
>> >> +				/* try SDMEM (but not MMC) even if SDIO is broken */
>> >> +				if (mmc_send_app_op_cond(host, 0, &ocr))
>> > In case of SDIO error, mmc_power_off() is getting called as part of
>> > mmc_detach_bus().  Shouldn't we power up the host before checking for
>> > SDMEM? Any comments?
>> I think you should ask Michal Miroslaw, as he wrote the patch for the
>> SD-combo (IO + mem)*
>>
>> But yes, in case of a failure, mmc_attach_sdio() will call
>> mmc_detach_bus()
>> which in turn will call mmc_power_off()
>>
>> And so it should be mmc_power_up() again before trying to detect SD
>> memory.
>
> Yes, you are right!  This explains some things...
>
> Please try attached patch. (Not tested, but obvious enough.)

I was looking at the code and figured out this issue. I don't have any
SD-combo card to verify your patch.

Thanks
Sahitya.
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora
Forum.

> Best Regards,
> Micha³ Miros³aw
>
> ---
>
> mmc: fix detection of memory part of SD-combo card with broken SDIO
>
> In case of failure, mmc_attach_sdio() will power off the SD bus.
> Power it up and reinitialize before trying SD memory detection.
>
> Reported-by: Sahitya Tummala <stummala@codeaurora.org>
> Signed-off-by: Micha³ Miros³aw <mirq-linux@rere.qmqm.pl>
> ---
>  drivers/mmc/core/core.c |    5 +++++
>  1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/mmc/core/core.c b/drivers/mmc/core/core.c
> index 6286898..32a4798 100644
> --- a/drivers/mmc/core/core.c
> +++ b/drivers/mmc/core/core.c
> @@ -1564,6 +1564,11 @@ void mmc_rescan(struct work_struct *work)
>  				 * Try SDMEM (but not MMC) even if SDIO
>  				 * is broken.
>  				 */
> +				mmc_power_up(host);
> +				sdio_reset(host);
> +				mmc_go_idle(host);
> +				mmc_send_if_cond(host, host->ocr_avail);
> +
>  				if (mmc_send_app_op_cond(host, 0, &ocr))
>  					goto out_fail;
>
> --
> 1.7.2.3
>
>

  reply	other threads:[~2010-12-03  5:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 21:34 [PATCH v4] mmc: Make ID freq configurable Hein_Tibosch
2010-09-03  1:47 ` Chris Ball
2010-09-03 23:25   ` Andrew Morton
2010-09-05 20:14 ` Matt Fleming
2010-09-05 20:43   ` Chris Ball
2010-09-05 21:22     ` Matt Fleming
2010-09-06  1:37       ` [PATCH v5] " Hein_Tibosch
2010-12-02 11:16 ` [PATCH v4] " Sahitya Tummala
2010-12-02 21:21   ` Hein_Tibosch
2010-12-02 22:38     ` Michal Miroslaw
2010-12-03  5:05       ` stummala [this message]
2010-12-03  6:56         ` Michal Miroslaw
2010-12-17  1:09       ` Chris Ball

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=1c6eadd860e1a9085336bf75a2a96eb3.squirrel@www.codeaurora.org \
    --to=stummala@codeaurora.org \
    --cc=adrian.hunter@nokia.com \
    --cc=akpm@linux-foundation.org \
    --cc=bn@niasdigital.com \
    --cc=cjb@laptop.org \
    --cc=hein_tibosch@yahoo.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=matt@console-pimps.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --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