From: Pierre Ossman <drzeus-list@drzeus.cx>
To: LAK <linux-arm-kernel@lists.arm.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
David Singleton <dsingleton@mvista.com>,
Philip Langdale <philipl@overt.org>,
"Brandt, Todd E" <todd.e.brandt@intel.com>,
Stanley Cai <stanley.w.cai@gmail.com>
Subject: [RFC][PATCH] MMC: Major restructuring and cleanup
Date: Thu, 04 Jan 2007 08:59:14 +0100 [thread overview]
Message-ID: <459CB3D2.4010707@drzeus.cx> (raw)
(This mail is cross-posted in order to reach the people most affected, so make sure you edit your receiver list when replying)
Hi everyone,
As I've mentioned to some of you, I've been working on restructuring the MMC layer in order to make it more easily maintained and to allow extensions like SDIO support. A first draft of this is now
ready for public review. I've cc:d those who have been waiting for this patch set (and Russell since he always gives blunt, but valuable feedback ;)).
Because of the size of the thing I decided to not attach it, but instead publish it in my public git tree:
http://www.kernel.org/git/?p=linux/kernel/git/drzeus/mmc.git;a=log;h=mmc-ng
One major mess right now is that the MMC layer handles two tasks: arbitrating who gets access to buses and cards, and initialising new cards as they are discovered. These two are currently intertwined
and it is difficult to get a decent overview of the system.
This first draft tries to solve this by moving all protocol stuff to their own files. The new core simply identifies what type of card that is present, then delegates the rest of the initialisation.
The commits themselves are a bit rough and will be more fine grained in a final version, but the end result should be the same. So I'd like to get as much input as possible from anyone who has the
time to review it. There are lots of changes, so I'm bound to have made mistakes in a few places.
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 reply other threads:[~2007-01-04 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 7:59 Pierre Ossman [this message]
2007-01-14 5:27 ` [RFC][PATCH] MMC: Major restructuring and cleanup Philip Langdale
2007-01-14 13:06 ` Pierre Ossman
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=459CB3D2.4010707@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=dsingleton@mvista.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=philipl@overt.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=stanley.w.cai@gmail.com \
--cc=todd.e.brandt@intel.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