From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/7] ARM: U300: set f_max to 24 MHz for MMCI
Date: Sun, 21 Feb 2010 21:07:40 +0000 [thread overview]
Message-ID: <20100221210740.GA3528@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1266537931-12560-1-git-send-email-linus.walleij@stericsson.com>
On Fri, Feb 19, 2010 at 01:05:31AM +0100, Linus Walleij wrote:
> This employs the frequency setting mechanism introduced to the
> MMCI to specify that this system can actually be clocked at 24 MHz.
>
> Signed-off-by: Linus Walleij <linus.walleij@stericsson.com>
> ---
> arch/arm/mach-u300/mmc.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-u300/mmc.c b/arch/arm/mach-u300/mmc.c
> index 109f5a6..c1cb977 100644
> --- a/arch/arm/mach-u300/mmc.c
> +++ b/arch/arm/mach-u300/mmc.c
> @@ -101,6 +101,7 @@ int __devinit mmc_init(struct amba_device *adev)
> * we have a regulator we can control instead.
> */
> /* Nominally 2.85V on our platform */
> + mmci_card->mmc0_plat_data.f_max = 24000000;
I bet setting this without DMA support leads to overruns/underruns on
the interface. That's why MMCI has a low default - to ensure that PIO
mode can keep up with the data transfers; the low maximum isn't because
of something to do with ARM platforms.
next prev parent reply other threads:[~2010-02-21 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 0:05 [PATCH 3/7] ARM: U300: set f_max to 24 MHz for MMCI Linus Walleij
2010-02-21 21:07 ` Russell King - ARM Linux [this message]
2010-02-22 20:42 ` Linus Walleij
2010-02-24 12:50 ` Russell King - ARM Linux
2010-02-24 14:35 ` Linus Walleij
2010-02-24 14:40 ` Russell King - ARM Linux
2010-02-24 20:10 ` Linus Walleij
2010-02-24 21:25 ` Linus Walleij
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=20100221210740.GA3528@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).