From: Magnus Damm <magnus.damm@gmail.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Simon Horman <horms@verge.net.au>,
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 08:55:55 +0000 [thread overview]
Message-ID: <AANLkTin0gELFYS2qCcB_FyGkAdwMQ_-LosDg2PKprqpp@mail.gmail.com> (raw)
In-Reply-To: <20110120083801.GB13114@linux-sh.org>
On Thu, Jan 20, 2011 at 5:38 PM, Paul Mundt <lethal@linux-sh.org> wrote:
> On Thu, Jan 20, 2011 at 05:28:55PM +0900, Magnus Damm wrote:
>> On Thu, Jan 20, 2011 at 4:07 PM, Simon Horman <horms@verge.net.au> wrote:
>> > 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.
>>
>> It most likely would. Perhaps it's worth adjusting the shared clock a
>> bit to support 20MHz?
>>
> "Most likely" isn't a constructive performance metric. It's worth trying
> out, and if it helps then of course it makes sense to try and support.
> It's not really worth going through and adding in additional complexity
> in order to support every possible frequency just becase we can, however.
Yes. Thanks for the "constructive performance metric". =)
next prev parent reply other threads:[~2011-01-20 8:55 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
2011-01-20 8:28 ` Magnus Damm
2011-01-20 8:38 ` Paul Mundt
2011-01-20 8:55 ` Magnus Damm [this message]
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=AANLkTin0gELFYS2qCcB_FyGkAdwMQ_-LosDg2PKprqpp@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=arnd@arndnet.de \
--cc=g.liakhovetski@gmx.de \
--cc=horms@verge.net.au \
--cc=lethal@linux-sh.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).