From: Ben Dooks <ben-linux@fluff.org>
To: linux-kernel@vger.kernel.org, drzeus-mmc@drzeus.cx
Subject: MMC test driver - help with output
Date: Fri, 20 Jun 2008 12:15:53 +0100 [thread overview]
Message-ID: <20080620111553.GC21835@fluff.org.uk> (raw)
I'm testing the s3c24xx sd/mmc driver and can't find any
documentation for each of the tests the mmc_test driver is
doing.
The following is output from a recent linux-next+driver:
[root@ ~]# echo > /sys/class/mmc_host/mmc0/mmc0\:0001/test
mmc0: Starting tests of card mmc0:0001...
mmc0: Test case 1. Basic write (no data verification)...
mmc0: Result: OK
mmc0: Test case 2. Basic read (no data verification)...
mmc0: Result: OK
mmc0: Test case 3. Basic write (with data verification)...
mmc0: Result: OK
mmc0: Test case 4. Basic read (with data verification)...
mmc0: Result: OK
mmc0: Test case 5. Multi-block write...
mmc0: Warning: Host did not wait for busy state to end.
mmc0: Result: OK
mmc0: Test case 6. Multi-block read...
mmc0: Result: OK
mmc0: Test case 7. Power of two block writes...
mmc0: Result: UNSUPPORTED (by card)
mmc0: Test case 8. Power of two block reads...
s3c2440-sdi s3c2440-sdi: unfinished read - pio_count:[0] pio_words:[0]
mmc0: Result: UNSUPPORTED (by host)
=> probably the wrong error being returned, but what would be
the general problem with this causing a finish before the driver
has decided that there should have been data to read?
mmc0: Test case 9. Weird sized block writes...
mmc0: Result: UNSUPPORTED (by card)
mmc0: Test case 10. Weird sized block reads...
s3c2440-sdi s3c2440-sdi: unfinished read - pio_count:[0] pio_words:[0]
mmc0: Result: UNSUPPORTED (by host)
mmc0: Test case 11. Badly aligned write...
mmc0: Result: OK
mmc0: Test case 12. Badly aligned read...
mmc0: Result: OK
mmc0: Test case 13. Badly aligned multi-block write...
mmc0: Warning: Host did not wait for busy state to end.
mmc0: Warning: Host did not wait for busy state to end.
mmc0: Warning: Host did not wait for busy state to end.
mmc0: Result: OK
mmc0: Test case 14. Badly aligned multi-block read...
mmc0: Result: OK
mmc0: Test case 15. Correct xfer_size at write (start failure)...
s3c2440-sdi s3c2440-sdi: bad data crc (incoming)
=> is this sort of error what was exepected?
mmc0: Result: ERROR (-84)
mmc0: Test case 16. Correct xfer_size at read (start failure)...
s3c2440-sdi s3c2440-sdi: data timeout
mmc0: Result: OK
=> is this the expected response?
mmc0: Test case 17. Correct xfer_size at write (midway failure)...
s3c2440-sdi s3c2440-sdi: bad data crc (incoming)
mmc0: Result: ERROR (-84)
mmc0: Test case 18. Correct xfer_size at read (midway failure)...
s3c2440-sdi s3c2440-sdi: data timeout
mmc0: Result: OK
mmc0: Tests completed.
[root@ ~]#
Also, any indications of how the "busy state" warnings could be
debugged?
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next reply other threads:[~2008-06-20 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 11:15 Ben Dooks [this message]
2008-06-20 17:41 ` MMC test driver - help with output 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=20080620111553.GC21835@fluff.org.uk \
--to=ben-linux@fluff.org \
--cc=drzeus-mmc@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
/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