From: Pierre Ossman <drzeus@drzeus.cx>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: ARM Linux Mailing List <linux-arm-kernel@lists.arm.linux.org.uk>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Marc Pignat <marc.pignat@hevs.ch>
Subject: Re: mmc_test : some results
Date: Mon, 9 Jun 2008 13:08:54 +0200 [thread overview]
Message-ID: <20080609130854.2237c05a@mjolnir.drzeus.cx> (raw)
In-Reply-To: <48495843.1050902@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
On Fri, 06 Jun 2008 17:31:15 +0200
Nicolas Ferre <nicolas.ferre@atmel.com> wrote:
> Hi Pierre,
>
> Here are the results of a mmc_test run played on at91_mci after applying
> this patch series :
> http://lkml.org/lkml/2008/5/30/201
>
> I skipped some of the tests just to concentrate on those ones.
>
> Can you tell me if the test is correct : are the errors reported for the
> xfer_size tests the normal behavior (I assume yes because a failure is
> simulated) ?
No. You're supposed to get an OK there as well. Basically it tests that
the driver doesn't report some unexpected error (-ETIMEDOUT is the
desired one) or overreports the number of written bytes.
>
> ~ # echo 1 > /sys/class/mmc_host/mmc0/mmc0\:e624/test
FYI, I've added some changes that will make that invocation only run
test 1. Do echo "" for all tests in the future.
Rgds
Pierre
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-09 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 15:31 Nicolas Ferre
2008-06-09 0:21 ` Gururaja Hebbar K R
2008-06-09 7:54 ` Nicolas Ferre
2008-06-09 11:08 ` Pierre Ossman [this message]
2008-06-10 9:27 ` [PATCH] at91_mci: manage cmd error and data error independently 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=20080609130854.2237c05a@mjolnir.drzeus.cx \
--to=drzeus@drzeus.cx \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.pignat@hevs.ch \
--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
all inboxes | Powered by JetHome®