From: Adrian Hunter <adrian.hunter@intel.com>
To: Shridhar Rasal <shri.rasal@gmail.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: mmc_test
Date: Tue, 14 Feb 2012 09:50:53 +0200 [thread overview]
Message-ID: <4F3A125D.8000603@intel.com> (raw)
In-Reply-To: <CAMKhXh=5eymTCzDPRd0ipxQN5z4ZB2BSoTxwy1C+v7iP8T_BiQ@mail.gmail.com>
On 14/02/12 08:41, Shridhar Rasal wrote:
> [sorry for spamming you]
>
> Dear Adrian,
>
> I am working on K3.1.
> I am trying to run mmc_test on my set-up. I have added mmc_test as a driver.
> But sysfs entries(test/testlist) are getting created only for any of SDIO host.
mmc_test will not work if mmc_block has already been given all the
MMC devices.
You can always switch between mmc_test and mmc_block by
unbinding / binding e.g.
# ls -al /sys/bus/mmc/drivers/mmcblk
drwxr-xr-x 2 root 0 0 Jan 1 00:00 .
drwxr-xr-x 4 root 0 0 Jan 1 00:00 ..
--w------- 1 root 0 4096 Jan 1 00:01 bind
lrwxrwxrwx 1 root 0 0 Jan 1 00:01 mmc0:0001 ->
../../../../devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001
--w------- 1 root 0 4096 Jan 1 00:01 uevent
--w------- 1 root 0 4096 Jan 1 00:01 unbind
# echo mmc0:0001 > /sys/bus/mmc/drivers/mmcblk/unbind
# echo mmc0:0001 > /sys/bus/mmc/drivers/mmc_test/bind
[ 128.221313] mmc_test mmc0:0001: Card claimed for testing.
>
> I digged further and found that,
> 1. mmc_test_probe is invoked only in case of SDIO and not for other hosts.
> 2. this is because of from mmc_bus_probe( ), only for SDIO host -
> mmc_test_probe () invoked and for other hosts - mmc_blk_probe () invoked.
>
>
> - What can be reason for this?
> - Am I missing some patches?
>
> Also, please let me know, where can I post such mmc related queries.
MMC mailing list:
http://vger.kernel.org/vger-lists.html#linux-mmc
next parent reply other threads:[~2012-02-14 7:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMKhXh=5eymTCzDPRd0ipxQN5z4ZB2BSoTxwy1C+v7iP8T_BiQ@mail.gmail.com>
2012-02-14 7:50 ` Adrian Hunter [this message]
2012-02-14 8:06 ` mmc_test Shashidhar Hiremath
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=4F3A125D.8000603@intel.com \
--to=adrian.hunter@intel.com \
--cc=linux-mmc@vger.kernel.org \
--cc=shri.rasal@gmail.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