All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: jh80.chung@samsung.com
Cc: kyungmin.park@samsung.com, ben-linux@fluff.org,
	linux-mmc@vger.kernel.org
Subject: Re: [PATCH] mmc: change initial clock setting
Date: Sat, 26 Jun 2010 17:57:45 +0100	[thread overview]
Message-ID: <87tyopg29i.fsf@linux-g6p1.site> (raw)
In-Reply-To: <4C1EEAA1.4020005@samsung.com>

On Mon, 21 Jun 2010 13:29:21 +0900, Jaehoon Chung <jh80.chung@samsung.com> wrote:
> On 2010-06-18 오후 9:42, Matt Fleming wrote:
> > On Fri, 18 Jun 2010 13:05:44 +0900, Jaehoon Chung <jh80.chung@samsung.com> wrote:
> >> This patch is bug fixed..
> >> I think that host->ios.clock(initial clock) will be set lower than 400KHz.
> >> But in this code, if host->f_min is higher than 400KHz, print warning message and set higher than 400KHz.
> >> And We use SDHCI_QUIRK_NONSTANDARD_CLOCK..so using get_min_clock function. 
> >> but didn't effect nothing through used get_min_clock function.
> > 
> > I'm a little confused. What problem are you fixing with this patch? What
> > issue are you seeing? SDHCI_QUIRK_NONSTANDARD_CLOCK is only for sdhci.
> > If this is the old "my card won't initialise at 400kHz" chestnut I don't
> > think a solution has ever been agreed upon. The problem was that while
> > some cards won't initialise at 400kHz, some controllers will try to
> > initialise at too low a frequency which causes other problems.
> > 
> > Sascha Hauer explains the reason for setting ios.clock to 400kHz here,
> > 
> >        http://lkml.org/lkml/2010/1/5/120
> > 
> > So I think your patch will cause problems.
> > 
> > Which driver are you using? The driver should have set the f_min value
> > to be <= 400kHz. Maybe it is a good idea to set the value of ios.clock
> > to 400kHz if the driver has set a bogus f_min value, we will at least
> > have a fighting chance of initialising the card (though I would say that
> > the driver was broken, but at least core.c will print a warning).
> > 
> 
> when ios.clock is higher than 400KHz, why not change 400KHz?(if 400KHz seemed like good value)
> if clock value is higher than 400KHz, i think card can't initialize...maybe

I think this part of your patch is OK.

> when sdhci controller set f_min value(ie, 300KHz), clock changed 400KHz in core.c.
> just this code purpose to print warning message?

Well, the purpose of the code is to set the clock to 400kHz if the value
of f_min is too low, as having a low value can cause some controllers to
break.

      reply	other threads:[~2010-06-26 16:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-18  4:05 [PATCH] mmc: change initial clock setting Jaehoon Chung
2010-06-18 12:42 ` Matt Fleming
2010-06-21  4:29   ` Jaehoon Chung
2010-06-26 16:57     ` Matt Fleming [this message]

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=87tyopg29i.fsf@linux-g6p1.site \
    --to=matt@console-pimps.org \
    --cc=ben-linux@fluff.org \
    --cc=jh80.chung@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    /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.