From: Rob Emanuele <poorarm@shoreis.com>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: Joey Oravec <joravec@drewtech.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
linux-kernel@vger.kernel.org,
Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: Re: [PATCH][Updated] New AT91 MCI Driver that supports both MCI slots used at the same time
Date: Mon, 8 Jun 2009 11:59:06 -0700 [thread overview]
Message-ID: <c8284b5b0906081159k2dc03216qcf2aa224fa06d0be@mail.gmail.com> (raw)
In-Reply-To: <c8284b5b0906080958o65a97a8dm914aa8b4c6e7a821@mail.gmail.com>
Haavard,
I'll revise my previous thought about integrating my changes back into
the Atmel driver. I'll start that today. I figure this way, the
changes I make can get in front of a wider audience.
Thanks,
Rob
On Mon, Jun 8, 2009 at 9:58 AM, Rob Emanuele<poorarm@shoreis.com> wrote:
> Hi Haavard,
>
> I'd be happy to reintegrate my changes to this back into the Atmel
> driver once I get it working correct on the at91. Do you have the
> equipment to give my changes a try?
>
> Converting my #defines for the the features to cpu_is_xxx is easy
> enough. I'll take care of that.
>
> Thanks,
>
> Rob
>
> On Mon, Jun 8, 2009 at 3:47 AM, Haavard
> Skinnemoen<haavard.skinnemoen@atmel.com> wrote:
>> Rob Emanuele wrote:
>>> This driver is a port the Atmel AVR32 MCI driver which uses similar silicon.
>>
>> While I do understand the motivation for this patch, I was kind of
>> hoping we could reduce the number of drivers for the Atmel MCI
>> hardware, not increase it...
>>
>> So I think it would be much better if your changes were integrated into
>> one of the existing drivers.
>>
>>> Joey Oravec has mentioned that he has had better reliability with the chip
>>> he is using (AT91SAM9261) if the MMC controller is reset before each
>>> command. There is a compile time option to do just that.
>>
>> This could be a useful option for atmel-mci too.
>>
>>> Joey Oravec has stated that the Read and Write Proof functionality that
>>> prevents buffer overflows is not available on the AT91SAM9261. This was
>>> confirmed by Nicolas Ferre and also affects the AT91RM9200. This new
>>> patch excludes those register config bits.
>>
>> Preferably use the cpu_is_xxx() functions to achieve that. Perhaps even
>> wrap those tests inside a mci_has_xxproof() function to make it
>> clearer what you're testing for, and easier to change if we decide to
>> do the test based on version registers, etc. later.
>>
>> Haavard
>>
>
next prev parent reply other threads:[~2009-06-08 18:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 21:40 [PATCH] New AT91 MCI Driver that supports both MCI slots used at the same time Rob Emanuele
2009-05-29 15:27 ` Joey Oravec
2009-06-02 16:53 ` Rob Emanuele
2009-06-03 15:10 ` Nicolas Ferre
2009-06-03 15:45 ` Joey Oravec
2009-06-03 19:02 ` [PATCH][Updated] " Rob Emanuele
2009-06-08 10:47 ` Haavard Skinnemoen
2009-06-08 16:58 ` Rob Emanuele
2009-06-08 18:59 ` Rob Emanuele [this message]
2009-06-02 8:49 ` [PATCH] " Nicolas Ferre
2009-06-02 16:31 ` Rob Emanuele
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=c8284b5b0906081159k2dc03216qcf2aa224fa06d0be@mail.gmail.com \
--to=poorarm@shoreis.com \
--cc=haavard.skinnemoen@atmel.com \
--cc=hskinnemoen@atmel.com \
--cc=joravec@drewtech.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.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