public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: Chris Ball <cjb@laptop.org>
Cc: Huang Changming-R66093 <R66093@freescale.com>,
	Jaehoon Chung <jh80.chung@samsung.com>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Kyungmin Park <kyungmin.park@samsung.com>,
	"andy.ross@windriver.com" <andy.ross@windriver.com>
Subject: Re: [PATCH] mmc: duplicated trial with same freq when mmc_rescan_try_freq()
Date: Fri, 13 May 2011 11:16:04 +0900	[thread overview]
Message-ID: <4DCC9464.3020806@samsung.com> (raw)
In-Reply-To: <m3fwokypzv.fsf@pullcord.laptop.org>

Hi Chris..

My question is others..I agreed the using frequency table..

But my questions is this...
For example, if f_min is 300KHz, you can the below message.

mmc1: mmc_rescan_try_freq: trying to init card at 400000 Hz
mmc1: mmc_rescan_try_freq: trying to init card at 300000 Hz
mmc1: mmc_rescan_try_freq: trying to init card at 300000 Hz

In other words, first init card with 400KHZ, 
but second/third to init with 300KHz. 
i think not necessary that try to initialize the two times with 300KHz.

I want to know your opinion..

Regards,
Jaehoon Chung

Chris Ball wrote:
> Hi,
> 
> On Thu, May 12 2011, Huang Changming-R66093 wrote:
>> The required min frequency (f_min) is 400KHz during identify stage, is
>> it necessary to use the frequency table (freqs[], including 300KHz,
>> 200KHz and 100KHz)?
> 
> Yes.  Some hardware is buggy/out of compliance with the spec.
> 
> - Chris.


  reply	other threads:[~2011-05-13  2:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12  8:18 [PATCH] mmc: duplicated trial with same freq when mmc_rescan_try_freq() Jaehoon Chung
2011-05-12  8:57 ` Huang Changming-R66093
2011-05-12 11:18   ` Jaehoon Chung
2011-05-12 14:04   ` Chris Ball
2011-05-13  2:16     ` Jaehoon Chung [this message]
2011-05-13 16:18       ` Andy Ross
2011-05-13 16:48 ` 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=4DCC9464.3020806@samsung.com \
    --to=jh80.chung@samsung.com \
    --cc=R66093@freescale.com \
    --cc=andy.ross@windriver.com \
    --cc=cjb@laptop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox