From: Pierre Ossman <drzeus@drzeus.cx>
To: Nicolas Ferre <nicolas.ferre@rfo.atmel.com>
Cc: "??" <wux@landicorp.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
ARM Linux Mailing List <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: [PATCH] mmc: at91_mci: add multiwrite cap
Date: Thu, 9 Aug 2007 16:45:11 +0200 [thread overview]
Message-ID: <20070809164511.6f40fa7b@poseidon.drzeus.cx> (raw)
In-Reply-To: <46BB200F.5090300@rfo.atmel.com>
[-- Attachment #1: Type: text/plain, Size: 2173 bytes --]
On Thu, 09 Aug 2007 16:09:19 +0200
Nicolas Ferre <nicolas.ferre@rfo.atmel.com> wrote:
>
> Ok thank you : it was the point.
>
> Results : in brief :
> - there is work to be done ;-)
> - multiwrite test result is : OK
>
I'm starting to get the feeling that writing this test driver was a
good idea. :)
> I had to modify the mmc_test to workaround the driver being stuck.
> I attach the patch so you can figure out the testcase I ran :
>
> diff -u b/drivers/mmc/card/mmc_test.c b/drivers/mmc/card/mmc_test.c
> --- b/drivers/mmc/card/mmc_test.c
> +++ b/drivers/mmc/card/mmc_test.c
> @@ -149,7 +149,8 @@
> printk(KERN_INFO "%s: Testing reading power of two block
> sizes...\n", mmc_hostname(card->host));
>
> - for (i = 1;i <= 512;i <<= 1) {
> +// for (i = 1;i <= 512;i <<= 1) {
> + for (i = 512;i <= 512;i <<= 2) { /*must have size%4 == 0*/
> memset(&mrq, 0, sizeof(struct mmc_request));
>
> mrq.cmd = &cmd;
These "fixes" shouldn't be needed with the recent patch by Marc Pignat.
>
> And here is the output :
>
> With a SD card :
> root@at91sam9263ek:~$ mmc0: card is read-write
> mmc0: new SD card at address 0002
> mmc0: About to test mmc subsystem
> mmc0: Testing writing power of two block sizes...
> .<7>mmc0: starting CMD16 arg 00000200 flags 00000015
>
> mmc0: Result: OK
> mmc0: Testing reading power of two block sizes...
> mmc0: Result: OK
> mmc0: Testing correct bytes_xfered for a single block...
> mmc0: Result: OK
> mmc0: Testing correct bytes_xfered for multiple blocks...
> mmc0: Result: OK
This looks ok (although this test doesn't verify the more exotic cases
of updating bytes_xfered).
> I do not know if the OOps is due to a bad behavior of the driver
> during the wait for busy test...
>
I don't suppose you could do a bit more digging? I'm not getting that
crash here.
> And with a MMC : quite the same results but with :
>
> mmc0: Testing correct bytes_xfered for a single block...
> mmc0: Result: FAIL
>
This is very odd. Could you test some more MMC and SD cards and see if
this is just a fluke? This test shouldn't be card dependent.
Rgds
Pierre
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-08-09 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 9:52 [PATCH] mmc: at91_mci: add multiwrite cap Nicolas Ferre
2007-08-08 10:11 ` Pierre Ossman
2007-08-08 14:45 ` Nicolas Ferre
2007-08-08 15:01 ` Pierre Ossman
2007-08-09 14:09 ` Nicolas Ferre
2007-08-09 14:45 ` Pierre Ossman [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=20070809164511.6f40fa7b@poseidon.drzeus.cx \
--to=drzeus@drzeus.cx \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@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