mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-mmc@drzeus.cx>
To: JosephChan@via.com.tw
Cc: linux-kernel@vger.kernel.org, arnd@arndb.de, ben-linux@fluff.org
Subject: Re: [Patch 1/1 v5] via-sdmmc: VIA MSP card reader driver support
Date: Tue, 28 Apr 2009 21:49:47 +0200	[thread overview]
Message-ID: <20090428214947.7478e66b@mjolnir.ossman.eu> (raw)
In-Reply-To: <C80EF34A3D2E494DBAF9AC29C7AE4EB8090CA2D4@exchtp03.taipei.via.com.tw>

On Wed, 22 Apr 2009 01:35:29 +0800
JosephChan@via.com.tw wrote:

> -----Original Message-----
> From: Pierre Ossman [mailto:drzeus-mmc@drzeus.cx] 
> >> +	else if (ios->clock >=  5000000)
> >> +		clock = PCI_CLK_8M;
> >>+	else
> >>+		clock = PCI_CLK_375K;
> >>+
> 
> > This looks a bit strange. Why are you not comparing with the clock frequency you'll be setting?
> 
> Do you mean that we should check the current clock frequency before setting?

No. My point was that you compare with, for example, 5 MHz, but then
you set the clock to 8 MHz. This is very dangerous as you'll most
likely overclock things.


> 
> > You also need to set the bits stating if the controller supports the high-speed SD and/or MMC mode, otherwise the core won't go over 25/20 MHz.
> 
> 
> OK, we will add the following line in the via_init_mmc_host function:
> 
>        mmc->caps |= MMC_CAP_MMC_HIGHSPEED |MMC_CAP_SD_HIGHSPEED;
> 

You sure the controller handles MMC high-speed timings though? They are
different from SD high-speed, which is why there are two separate caps
bits.

Rgds
-- 
     -- Pierre Ossman

  Linux kernel, MMC maintainer        http://www.kernel.org
  rdesktop, core developer          http://www.rdesktop.org
  TigerVNC, core developer          http://www.tigervnc.org

  WARNING: This correspondence is being monitored by the
  Swedish government. Make sure your server uses encryption
  for SMTP traffic and consider using PGP for end-to-end
  encryption.

  reply	other threads:[~2009-04-28 19:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01  2:24 JosephChan
2009-04-10 18:35 ` Pierre Ossman
2009-04-10 18:37   ` Pierre Ossman
2009-04-21 17:35   ` JosephChan
2009-04-28 19:49     ` Pierre Ossman [this message]
2009-05-25  3:09     ` Harald Welte

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=20090428214947.7478e66b@mjolnir.ossman.eu \
    --to=drzeus-mmc@drzeus.cx \
    --cc=JosephChan@via.com.tw \
    --cc=arnd@arndb.de \
    --cc=ben-linux@fluff.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®