From: Nicolas Ferre <nicolas.ferre@rfo.atmel.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: ARM Linux Mailing List <linux-arm-kernel@lists.arm.linux.org.uk>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Andrew Victor <andrew@sanpeople.com>,
Andreas Beier <mughat@gmail.com>,
Hamish Guthrie <hamish@prodigi.ch>,
Marc Pignat <marc.pignat@hevs.ch>,
wux@landicorp.com,
Patrice Vilchez <patrice.vilchez@rfo.atmel.com>
Subject: Re: [PATCH] mmc: at91_mci: fix hanging and rework to match flowcharts
Date: Mon, 09 Jul 2007 14:48:45 +0200 [thread overview]
Message-ID: <46922EAD.5050802@rfo.atmel.com> (raw)
In-Reply-To: <4688FE50.7050806@drzeus.cx>
Pierre Ossman :
> Nicolas Ferre wrote:
>> Fixes hanging using multi block operations (seen during CMD25).
>> Follows closely the datasheet flowcharts.
>>
>> This piece of code handles better big file writing. I had to take care
>> of the notbusy signal during write (at91_mci_handle_cmdrdy function) and
>> to rearrange the AT91_MCI_ENDRX and AT91_MCI_RXBUFF flag usage.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@rfo.atmel.com>
>> ---
>
> Most of the patch looks ok. Do you want to wait for some more tests or should I
> chuck this into the imminent merge window?
*pong*
I think it is ok to put it into the merge window.
>> @@ -817,7 +834,11 @@ static int __init at91_mci_probe(struct
>> mmc->ops = &at91_mci_ops;
>> mmc->f_min = 375000;
>> - mmc->f_max = 25000000;
>> + if (cpu_is_at91sam9263())
>> + mmc->f_max = 50000000;
>> + else
>> + mmc->f_max = 25000000;
>> +
>> mmc->ocr_avail = MMC_VDD_32_33 | MMC_VDD_33_34;
>> mmc->caps = MMC_CAP_BYTEBLOCK | MMC_CAP_MULTIWRITE;
>>
>
> This seems unrelated to the rest of the patch. Also, high-speed won't be enabled
> unless you set the appropriate caps (which should be checked against timing
> specifications, not just assigned and hope for the best).
True. I remove this chunk off the patch.
>> @@ -830,11 +851,11 @@ static int __init at91_mci_probe(struct
>> host->bus_mode = 0;
>> host->board = pdev->dev.platform_data;
>> if (host->board->wire4) {
>> -#ifdef SUPPORT_4WIRE
>> - mmc->caps |= MMC_CAP_4_BIT_DATA;
>> -#else
>> - printk("AT91 MMC: 4 wire bus mode not supported by this driver
>> - using 1 wire\n");
>> -#endif
>> + if (cpu_is_at91sam9260() || cpu_is_at91sam9263())
>> + mmc->caps |= MMC_CAP_4_BIT_DATA;
>> + else
>> + printk("AT91 MMC: 4 wire bus mode not supported"
>> + " - using 1 wire\n");
>> }
>>
>> /*
>>
>
> This also looks unrelated.
Well, It is related to capacities of newer IPs that allow readproof and
writeproof features that I enable here :
+ if (cpu_is_at91sam9260() || cpu_is_at91sam9263())
+ mr |= AT91_MCI_RDPROOF | AT91_MCI_WRPROOF;
This allows to have a smooth data transmission internally (prevent
underruns) and so have full 4 wires capacity. So I think this is good
for having a full featured driver on all chips.
I resend a corrected patch now.
Regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2007-07-09 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 12:16 [PATCH] mmc: at91_mci: fix hanging and rework to match flowcharts Nicolas Ferre
2007-07-02 12:45 ` Marc Pignat
2007-07-02 13:32 ` Pierre Ossman
2007-07-09 10:51 ` Pierre Ossman
2007-07-09 12:48 ` Nicolas Ferre [this message]
2007-07-02 19:13 ` Mariusz Kozlowski
2007-07-09 12:58 ` Nicolas Ferre
2007-07-09 16:27 ` Pierre Ossman
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=46922EAD.5050802@rfo.atmel.com \
--to=nicolas.ferre@rfo.atmel.com \
--cc=andrew@sanpeople.com \
--cc=drzeus-list@drzeus.cx \
--cc=hamish@prodigi.ch \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.pignat@hevs.ch \
--cc=mughat@gmail.com \
--cc=patrice.vilchez@rfo.atmel.com \
--cc=wux@landicorp.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