From: Tony Lindgren <tony@atomide.com>
To: Hiroshi DOYU <Hiroshi.DOYU@nokia.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [patch 0/5] [RFC] MMC handle mutiple slots by external transceiver
Date: Mon, 20 Mar 2006 06:43:25 -0800 [thread overview]
Message-ID: <20060320144324.GC4980@atomide.com> (raw)
In-Reply-To: <20060308102705.c8713048.Hiroshi.DOYU@nokia.com>
* Hiroshi DOYU <Hiroshi.DOYU@nokia.com> [060308 00:31]:
> Hello,
>
> This patch series is intended basically to make MMC handle multiple bus(slots)
> when it uses an external transceiver. And this also can handle multiple
> SD cards at the same time. Basic idea is to deal with each slot independently
> during card detection phase until RCA number is assigned to each card,
> because an external transceiver can deal each slot separately(independently).
> After RCA number is assigned(after card detection), we can access a specified
> card which we want to use by choosing RCA number.
>
> Currently most of things is being handled by "drivers/mmc/omap.c" in order
> to keep current MMC common framework in "drivers/mmc/mmc.c" as it is. But
> I think that there might be an another alternative implementation to change
> MMC common framework itself to handle multiple bus with an external
> transceiver. So I would like to get some comments/feedbacks about this issue.
>
> This patch series include 5 patches and
> the main one is:
>
> [patch 2/5] MMC MULTIPLE SLOT SUPPORT BASE
>
> The others are small bugfixes and supplement ones.
Let's push these and once we have the Carlos' version of the MMC driver
integrated into the mainline kernel we start merging in the omap tree.
We probably will want to keep the existing MMC driver around for a
little while until everything is merged.
Tony
prev parent reply other threads:[~2006-03-20 14:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 8:27 [patch 0/5] [RFC] MMC handle mutiple slots by external transceiver Hiroshi DOYU
2006-03-20 14:43 ` Tony Lindgren [this message]
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=20060320144324.GC4980@atomide.com \
--to=tony@atomide.com \
--cc=Hiroshi.DOYU@nokia.com \
--cc=linux-omap-open-source@linux.omap.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