From: Pavel Machek <pavel@ucw.cz>
To: Ben Nizette <bn@niasdigital.com>
Cc: Pierre Ossman <pierre@ossman.eu>,
Adrian Hunter <adrian.hunter@nokia.com>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Matt Fleming <matt@console-pimps.org>,
Hein_Tibosch <hein_tibosch@yahoo.es>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH v2] mmc: lower init clock frequency to 300kHz
Date: Wed, 6 Jan 2010 08:01:42 +0100 [thread overview]
Message-ID: <20100106070141.GC1382@ucw.cz> (raw)
In-Reply-To: <2A48D9AC-90D7-405F-A64C-0703F5FEC175@niasdigital.com>
On Sat 2010-01-02 10:11:10, Ben Nizette wrote:
>
> A good few months ago, commit
>
> commit 8dfd0374be84793360db7fff2e635d2cd3bbcb21
> Author: Sascha Hauer <s.hauer@pengutronix.de>
> Date: Thu Apr 9 08:32:02 2009 +0200
>
> MMC core: limit minimum initialization frequency to 400kHz
>
> broke a few setups with cards which don't quite adhere to the MMC spec - 400kHz is just too fast for them. In my testing, all of the cards which fail at 400kHz are OK by about 350Khz but this patch drops the floor to 300 to be on the safe side.
>
> Dropping the floor also means that the warning will trigger on some valid setups, albeit ones which won't run particularly crappy cards. This patch then slightly softens the language of said warning to make it clear it isn't always a problem.
>
> V1 of this patch dropped the floor all the way to 50kHz on the basis that it was only for a few 100 bytes so that very low speed shouldn't matter. After some discussion [1] the consensus was that 50 was too slow after all so this patch is a bit more sensible.
>
(please wrap).
> @@ -891,12 +891,12 @@ static void mmc_power_up(struct mmc_host *host)
> */
> mmc_delay(10);
>
> - if (host->f_min > 400000) {
> - pr_warning("%s: Minimum clock frequency too high for "
> + if (host->f_min > 300000) {
> + pr_warning("%s: Minimum clock frequency may be too high for "
> "identification mode\n", mmc_hostname(host));
> host->ios.clock = host->f_min;
> } else
> - host->ios.clock = 400000;
> + host->ios.clock = 300000;
>
> host->ios.power_mode = MMC_POWER_ON;
> mmc_set_ios(host);
Machine with minimum clock of 1MHz is clearly broken, yet you issue
"soft" warning.
What about:
if (f_min > 400k)
print existing warning
else if (f_min > 300k)
print warning 'if your card does not work, its broken, but
your host is unhelpful'
clock = f_min
if (clock < 3o0)
clock = 300
?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2010-01-06 7:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-01 23:11 [PATCH v2] mmc: lower init clock frequency to 300kHz Ben Nizette
2010-01-06 7:01 ` Pavel Machek [this message]
2010-01-06 9:01 ` Hein_Tibosch
[not found] <1246492196.2980.17.camel@linux-51e8.site>
[not found] ` <20090702135849.21370282@hskinnemoen-d830>
[not found] ` <1246537056.2980.60.camel@linux-51e8.site>
[not found] ` <4B3E570C.2060602@yahoo.es>
[not found] ` <63809451-ED1D-487A-AE63-F72B23D136D8@niasdigital.com>
[not found] ` <4B3F019F.6010306@yahoo.es>
2010-01-02 9:07 ` Ben Nizette
2010-01-02 12:08 ` Pierre Ossman
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=20100106070141.GC1382@ucw.cz \
--to=pavel@ucw.cz \
--cc=adrian.hunter@nokia.com \
--cc=bn@niasdigital.com \
--cc=hein_tibosch@yahoo.es \
--cc=linux-kernel@vger.kernel.org \
--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