* Re: question for mmc_test
[not found] <25B60CDC2F704E4E9D88FFD52780CB4C0BDE9843EA@SC-VEXCH1.marvell.com>
@ 2013-02-28 7:21 ` Andy Shevchenko
0 siblings, 0 replies; only message in thread
From: Andy Shevchenko @ 2013-02-28 7:21 UTC (permalink / raw)
To: Kevin Liu; +Cc: linux-mmc
On Wed, 2013-02-27 at 22:15 -0800, Kevin Liu wrote:
> Andy,
Added linux-mmc@ ML.
> I never used mmc_test.c and I have several questions for it.
> 1. I have 3 sdh controllers (sd, emmc, sdio) in system, then which host does mmc_test test?
> 2. I found mmc_test always bind to sdio, so fail to add the debugfs.
> mmc_test_probe was not launched for sd and emmc, why?
It binds to the card. It seems you have sdio attached when module is
initialized.
> 3. Currently, I just build mmc_test in the kernel and didn't change anything.
> In git log, I found below comments written by you.
> Example of usage:
> # mount -t debugfs none /sys/kernel/debug
> # modprobe mmc_test
> [ 581.395843] mmc_test mmc0:0001: Card claimed for testing.
> # echo 25 > /sys/kernel/debug/mmc0/mmc0\:0001/test
> [ 604.568542] mmc0: Starting tests of card mmc0:0001...
> [ 604.582733] mmc0: Test case 25. Best-case read performance into scattered pages...
> [ 604.923553] mmc0: Transfer of 8192 sectors (4096 KiB) took 0.124664314 seconds (33644 kB/s, 32856 KiB/s)
> [ 604.933227] mmc0: Result: OK
> [ 604.936248] mmc0: Tests completed.
> # cat /sys/kernel/debug/mmc0/mmc0\:0001/test
>
> I can also make mmc_test build-in kernel, right? Do I miss anything?
Yes, you missed something.
You have to attach the card you would like to test, then go to the sysfs
and do unbind-bind cycle manually by echoing proper card ID.
I could ask Adrian if we could provide piece of documentation he wrote
few years ago at Nokia.
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
^ permalink raw reply [flat|nested] only message in thread