linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org,
	Arnd Hannemann <arnd@arndnet.de>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: SDHC Read Performance
Date: Thu, 20 Jan 2011 07:07:40 +0000	[thread overview]
Message-ID: <20110120070738.GA32495@verge.net.au> (raw)
In-Reply-To: <AANLkTi=fw1C0cj9U9=c0PxvOPHZtM66pDc+zpR9p=68c@mail.gmail.com>

On Thu, Jan 20, 2011 at 01:01:04PM +0900, Magnus Damm wrote:
> 1) Can you try a different SDHC Class 10 card? I'd just simply buy a
> top-of-the-line SanDisk card myself and try that, but anything
> different from what you're having is probably useful as a contrast.

Sure, will do.

> 2) How about the MMC4.0 down-clocking. Is there anything we can do
> about that software-wise?

As I understand it, the problem is that the SDHI allows a simple
divisor to applied to a clock source. Effectively this means
that the driver may use use 12Mhz, 24Mhz and 50Mhz.

In the case of MMC the desired speed is 20Mhz, but the highest
value from the list above that the driver can use is 12Mhz.

As we discussed (offline) yesterday, it ought to be possible
to change the frequency of the clock source. And in the case of
the mackerel this can probably be done without disturbing anything
else as there are per SHDI clock sources.

I imagine it would be possible to manipulate the frequency
such that MMC can be run closer to 20Mhz than 12Mhz.

However, I am unsure if this would improve performance in any way.


  reply	other threads:[~2011-01-20  7:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-19  0:09 SDHC Read Performance Simon Horman
2011-01-19  3:14 ` Magnus Damm
2011-01-19  8:05   ` Simon Horman
2011-01-20  3:30     ` Simon Horman
2011-01-20  4:01       ` Magnus Damm
2011-01-20  7:07         ` Simon Horman [this message]
2011-01-20  8:28           ` Magnus Damm
2011-01-20  8:38             ` Paul Mundt
2011-01-20  8:55               ` Magnus Damm
2011-03-21 22:38         ` Simon Horman
2011-03-21 22:55           ` Arnd Bergmann
2011-03-22  7:16             ` Simon Horman

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=20110120070738.GA32495@verge.net.au \
    --to=horms@verge.net.au \
    --cc=arnd@arndnet.de \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).