public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hein_Tibosch <hein_tibosch@yahoo.es>
To: Pierre Ossman <pierre@ossman.eu>
Cc: 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 v3] mmc: Make ID freq configurable
Date: Sun, 03 Jan 2010 16:00:09 +0800	[thread overview]
Message-ID: <4B404E89.4060103@yahoo.es> (raw)
In-Reply-To: <20100103003804.66021fe9@mjolnir.ossman.eu>

Pierre Ossman wrote:
> On Sun, 3 Jan 2010 09:23:30 +1100
> Ben Nizette <bn@niasdigital.com> wrote:
>
>   
>>> Broken cards seem to be all over the spectrum, so I wouldn't be
>>> suprised if you find ones that break if you go too low as well.
>>>       
>> Yea good point, though given there might not even be a One Freq to Rule Them All, how about:
>>
>> ---8<---
>>
>> From: Ben Nizette <bn@niasdigital.com>
>> Subject: [PATCH v3] mmc: Make ID freq configurable
>>
>> While the SD spec specifies a range of frequencies for the ID phase from 100-400kHz, not all cards play by the rules.  This patch adds a Kconfig option to allow the user to tweak this to their card/host config, though the default of 250kHz should be fine for all spec-abiding cards and most others besides.
>>
>> Signed-off-by: Ben Nizette <bn@niasdigital.com>
>>
>>     
>
> This is not a good solution. We all use the same pool of cards so we
> should all be using the same init sequence. If there isn't a single
> frequency where all cards will work, then we'll have to make something
> more advanced where the kernel will try the init several times with
> different clocking.
>   
As I'm lucky to have main-stream cards that break the rule (on
avr32/AP7) I'll dive deeper into it and see if I can make it "automatic"
so that initialization will work for any of cards. Indeed using a kind
of 'bisect approach' approach.
... although I must say that before Sascha Hauer's patch, we never had
problems with any of the cards, using the controller's minimum freq of
137 Khz.

Hein




  reply	other threads:[~2010-01-03  8:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-01 23:49 [PATCH] MMC Core: Drop initialization frequency floor to 50kHz Ben Nizette
2009-07-02  7:18 ` Pierre Ossman
2009-07-02 11:10   ` Ben Nizette
2009-07-02 11:58 ` Haavard Skinnemoen
2009-07-02 12:17   ` Ben Nizette
     [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           ` [PATCH v2] mmc: lower init clock frequency to 300kHz Ben Nizette
2010-01-02 12:08             ` Pierre Ossman
2010-01-02 22:23               ` [PATCH v3] mmc: Make ID freq configurable Ben Nizette
2010-01-02 23:04                 ` Robert Hancock
2010-01-02 23:38                 ` Pierre Ossman
2010-01-03  8:00                   ` Hein_Tibosch [this message]
2010-01-04 21:07                   ` Hein_Tibosch
2010-01-05 12:24                     ` Sascha Hauer
2010-01-04 21:58                   ` Hein_Tibosch
2010-08-27 20:44                     ` Chris Ball
2010-08-28  0:44                       ` 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=4B404E89.4060103@yahoo.es \
    --to=hein_tibosch@yahoo.es \
    --cc=adrian.hunter@nokia.com \
    --cc=bn@niasdigital.com \
    --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