From: Pierre Ossman <drzeus-list@drzeus.cx>
To: Philip Langdale <philipl@overt.org>
Cc: LAK <linux-arm-kernel@lists.arm.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] MMC: Major restructuring and cleanup
Date: Sun, 14 Jan 2007 14:06:31 +0100 [thread overview]
Message-ID: <45AA2AD7.70607@drzeus.cx> (raw)
In-Reply-To: <45A9BF57.7050408@overt.org>
Philip Langdale wrote:
> So, I think I'm a bit too much of a kernel newbie to be able to provide a
> definitive review, but I've looked over the changes and they look good to me.
>
Good to hear. I'd like to get this in ASAP, but in order to make sure
everyone gets a look at it, it'll have to go a round in -mm during the
next kernel.
> I fully agree with the rearchitecturing - it makes it a lot easier to see
> what's going on and it'll scale for SDIO (as you mention) and CE-ATA as well,
> if we ever get a hold of any of those :-)
>
With the very generous help of John Gilmore, I think we'll have those
sorted out in a jiffy. :)
> One concrete observation I'd make is that we should probably try and detect
> MMC first instead of SD. Up until today, I'd have said it didn't really
> matter, but I've been doing some reading and discovered that Protec make
> some very strange cards they call "SuperSD" which can talk mmc4 and sd 1.1.
> These will happily go along with either initialisation sequence - and as mmc4
> is either the same or better than sd 1.1 from a performance point of view,
> we should prefer it. This is independent of your restructuring, but as you're
> fiddling with this code... :-)
>
Eeeeww... This is a problem as the SD spec. clearly states the order of
init commands. So I wouldn't be surprised if we find SD cards that choke
on the MMC init sequence.
I guess what we lose by not supporting these is 8 bit data bus, but as
we do not currently have a controller for that I think the point is moot.
Rgds
--
-- Pierre Ossman
Linux kernel, MMC maintainer http://www.kernel.org
PulseAudio, core developer http://pulseaudio.org
rdesktop, core developer http://www.rdesktop.org
next prev parent reply other threads:[~2007-01-14 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 7:59 [RFC][PATCH] MMC: Major restructuring and cleanup Pierre Ossman
2007-01-14 5:27 ` Philip Langdale
2007-01-14 13:06 ` Pierre Ossman [this message]
2007-01-15 0:38 ` Philip Langdale
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=45AA2AD7.70607@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=philipl@overt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.