From: Magnus Damm <magnus.damm@gmail.com>
To: Ian Molton <ian@mnementh.co.uk>
Cc: Pierre Ossman <drzeus@drzeus.cx>,
linux-kernel@vger.kernel.org, drzeus-wbsd@drzeus.cx,
akpm@linux-foundation.org
Subject: Re: [PATCH 00/05] tmio_mmc: Minor fixes and cnf/irq changes
Date: Wed, 25 Mar 2009 17:56:31 +0900 [thread overview]
Message-ID: <aec7e5c30903250156v1eb38bd7qafe1c4236d9daef@mail.gmail.com> (raw)
In-Reply-To: <49C84060.6010903@mnementh.co.uk>
On Tue, Mar 24, 2009 at 11:07 AM, Ian Molton <ian@mnementh.co.uk> wrote:
> Magnus Damm wrote:
>
>> Thanks for your help. I was hoping on getting patch 3 and 4 included
>> in 2.6.30 as well if possible. I suspect that i have to rework them a
>> bit first though. That's no problem. Just let me know how you guys
>> prefer things and i'll resend.
>
> Can you clarify how your platform actually controls the MMC clock? does it
> at all?
I don't know. The block is embedded in an SoC and I have no
documentation. I assume there is some kind of clock hooked up to the
hardware block, and making use of that should be quite simple since we
already have clock framework support in place for the processor.
> what is your platform?
With tmio_mmc and the posted patches in this series I can use some
platform data to improve MMC performance. So far MMC support looks
like this:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=70e5c4f0843c3021a2e95b46edd8925a885d2e31
I think the MMC performance can be improved about 100x with tmio_mmc,
so it would be great to get this working. =)
> Ideally, the MMC code would use the clock API for some of this, but I seem
> to remember there were issues with this (cant recall what right now and its
> 2:05 AM).
No worries. For me the clock framework would be the best fit too. Not
sure about the exact details right now, but I _do_ know that we right
now we have nothing, so being able to use tmio_mmc as is (with posted
patches) is a great step forward. Working out the clock framework
details after that should be no biggie. Step by step.
Or if you want me to rewrite things that's fine as well. Just let me
know what to do. =)
Thanks for your help!
/ magnus
next prev parent reply other threads:[~2009-03-25 8:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-11 12:58 Magnus Damm
2009-03-11 12:58 ` [PATCH 01/05] tmio_mmc: Fix one off, use resource_size() in probe() Magnus Damm
2009-03-11 14:26 ` Ian Molton
2009-03-11 12:59 ` [PATCH 02/05] tmio_mmc: Fix use after free in remove() Magnus Damm
2009-03-11 14:28 ` Ian Molton
2009-03-11 12:59 ` [PATCH 03/05] tmio_mmc: Break out cnf area operations Magnus Damm
2009-03-11 14:39 ` Ian Molton
2009-03-12 2:13 ` Magnus Damm
2009-03-11 12:59 ` [PATCH 04/05] tmio_mmc: Make cnf area optional Magnus Damm
2009-03-11 12:59 ` [PATCH 05/05] tmio_mmc: Support multiple interrupts Magnus Damm
2009-03-11 14:21 ` Ian Molton
2009-03-12 1:45 ` Magnus Damm
2009-03-16 18:30 ` [PATCH 00/05] tmio_mmc: Minor fixes and cnf/irq changes Pierre Ossman
2009-03-18 1:58 ` Magnus Damm
2009-03-24 2:07 ` Ian Molton
2009-03-25 8:56 ` Magnus Damm [this message]
2009-03-31 2:51 ` Magnus Damm
2009-03-31 18:37 ` Ian Molton
2009-04-01 2:20 ` Magnus Damm
2009-04-01 19:00 ` Ian Molton
2009-03-24 2:00 ` Ian Molton
2009-03-24 20:05 ` Pierre Ossman
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=aec7e5c30903250156v1eb38bd7qafe1c4236d9daef@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=drzeus-wbsd@drzeus.cx \
--cc=drzeus@drzeus.cx \
--cc=ian@mnementh.co.uk \
--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®