All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sheetal <sheetal.tigadoli@gmail.com>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: mmc_test.ko usage
Date: Mon, 12 Oct 2015 12:58:22 +0530	[thread overview]
Message-ID: <561B6116.6070206@gmail.com> (raw)
In-Reply-To: <CAHhAz+gv2dpozYdZu9aEa4iT8Dv0=+CMN-jjd6vP1tJ-08PeZQ@mail.gmail.com>


On Monday 12 October 2015 12:11 PM, Muni Sekhar wrote:
> On Mon, Oct 12, 2015 at 11:40 AM, Sheetal <sheetal.tigadoli@gmail.com> wrote:
>> On Monday 12 October 2015 11:25 AM, Muni Sekhar wrote:
>>> Hi ,
>>>
>>>
>>> I tried to use the MMC host test driver (mmc_test.ko) for testing SD
>>> Host controller hardware. When I load the driver I noticed that
>>> mmc_test_probe() not getting called.
>>>
>>> Could anyone specify the exact usage of mmc_test.ko?
>>>
>> Hello Muni Sekhar,
>>
>> I think the following might help you in using MMC_TEST.KO Module
>>
>> 0. insmod mmc_test.ko
>> 1. unbind the mmc block driver
>> echo mmc0:b368 > /sys/bus/mmc/drivers/mmcblk/unbind
>> 2. bind the mmc_test driver
>> echo mmc0:b368 > /sys/bus/mmc/drivers/mmc_test/bind
>> 3. mount the debugfs if you don't mount for debugfs
>> mount -t debugfs none /sys/kernel/debug
>> 4. After mount, you can see the "/sys/kernel/debug/mmc0/mmc0:b368/test"
>> 5. echo "test number" > /sys/kernel/debug/mmc0/mmc0\:b368/test
>> you can see the "test number" using the "cat
>> /sys/kernel/debug/mmc0/mmc0\:b368/testlist"
>>
>> The above has been copied straigtly from thelink
>> <http://forum.kernelnewbies.org/read.php?12,1991,116405#msg-116405>
>>
>
>
> Hello Sheetal,
>
>
>
> Thanks for the quick reply. I followed the steps but nmcblk unbind
> fails “bash: echo: write error: No such device”. Any idea about this
> failure?
>
>
>
> # echo mmc0:b368 > /sys/bus/mmc/drivers/mmcblk/unbind
>
> bash: echo: write error: No such device
>
>
>
>
> # ls -al /sys/bus/mmc/drivers/mmcblk
>
> total 0
>
> drwxr-xr-x 2 root root    0 Oct 12 11:49 .
>
> drwxr-xr-x 4 root root    0 Oct 12 11:49 ..
>
> --w------- 1 root root 4096 Oct 12 11:52 bind
>
> --w------- 1 root root 4096 Oct 12 11:49 uevent
>
> --w------- 1 root root 4096 Oct 12 11:52 unbind
>
>
>
> --
> Thanks,
> Sekhar
Hello Muni Sekhar,

You have to find the device node that has been created, In the example 
it was "mmc0:b368"
and appropriately modify the echo statement and every other statement 
where it is referenced

Thanks & Regards

      reply	other threads:[~2015-10-12  7:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12  5:55 mmc_test.ko usage Muni Sekhar
2015-10-12  6:10 ` Sheetal
2015-10-12  6:41   ` Muni Sekhar
2015-10-12  7:28     ` Sheetal [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=561B6116.6070206@gmail.com \
    --to=sheetal.tigadoli@gmail.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=munisekharrms@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.