From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: Rob Emanuele <poorarm@shoreis.com>,
Andrew Victor <avictor.za@gmail.com>,
Joey Oravec <joravec@drewtech.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
linux-kernel@vger.kernel.org, drzeus-mmc@drzeus.cx
Subject: Re: [PATCH][Fix] New Unified AVR32/AT91 MCI Driver that supports both MCI slots used at the same time
Date: Mon, 15 Jun 2009 16:51:18 +0200 [thread overview]
Message-ID: <4A365FE6.8080908@atmel.com> (raw)
In-Reply-To: <20090612112900.4435f70f@hskinnemoen-d830>
Haavard Skinnemoen :
> Nicolas Ferre wrote:
>>> Well, what is the best way to differentiate it from the at91_mci
>>> driver and keep users from trying to use both drivers?
>> I propose that we setup a kind of choice sub menu in the Kconfig for
>> those two drivers when they are both supported.
>
> Shouldn't it be enough to simply add
>
> depends on !THE_OTHER_DRIVER
>
> to both of them?
It does not seems to work...
> Btw, what are the long-term plans for this? Should the at91_mci driver
> be phased out once the atmel-mci driver supports all at91 and avr32
> devices?
In my opinion, it is a bit early to tell. My thoughts were that I
suspect we should keep at91_mci for at91rm9200 and at91sam9261/9261s as
they contain an older revision of the MCI IP. In the meantime, Rob tend
to integrate also code to manage those chips (without RDPROOF/WRPROOF
switch).
So, lets see how far we can go with the atmel-mci on at91 chips and
then, consider a phase out.
Regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2009-06-15 14:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-10 23:41 [PATCH][Fix] New Unified AVR32/AT91 MCI Driver that supports both MCI slots used at the same time (was: [PATCH][Updated] New AT91 MCI Driver that supports both MCI slots used at the same time) Rob Emanuele
2009-06-11 7:54 ` [PATCH][Fix] New Unified AVR32/AT91 MCI Driver that supports both MCI slots used at the same time Haavard Skinnemoen
2009-06-11 20:16 ` Rob Emanuele
2009-06-12 9:03 ` Nicolas Ferre
2009-06-12 9:29 ` Haavard Skinnemoen
2009-06-15 14:51 ` Nicolas Ferre [this message]
2009-06-12 18:18 ` Rob Emanuele
2009-06-12 12:37 ` Nicolas Ferre
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=4A365FE6.8080908@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=avictor.za@gmail.com \
--cc=drzeus-mmc@drzeus.cx \
--cc=haavard.skinnemoen@atmel.com \
--cc=joravec@drewtech.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=poorarm@shoreis.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 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.