All of lore.kernel.org
 help / color / mirror / Atom feed
From: J Freyensee <james_p_freyensee@linux.intel.com>
To: Shashidhar Hiremath <shashidharh@vayavyalabs.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Chris Ball <cjb@laptop.org>,
	John Calixto <john.calixto@modsystems.com>,
	linux-mmc@vger.kernel.org
Subject: Re: A question on IOCTL interface for MMC
Date: Mon, 24 Oct 2011 11:28:52 -0700	[thread overview]
Message-ID: <4EA5AE64.2030106@linux.intel.com> (raw)
In-Reply-To: <CANYdXnoS31GLnbFcwj76SUoyVhcti8Q-4_5fmyRy3DUJGbSRjg@mail.gmail.com>

On 10/24/2011 05:32 AM, Shashidhar Hiremath wrote:
> Hi Arnd,
>    As explained in previous mail, the IOCTL is actually an inteface to
> block layer and it is only expecting read/write commands to be sent
> through the interface.The prrof of it can be seen in write_flag
> present in the IOCTL structure which indicates the either the command
> can be read or a write command.
>
> So, can I submit a linux module to the kernel which uses the same
> mmc_ioc_cmd structure and do all the required processing in my module.
>
> To be clear on my requirement:
> it is  To test ALL SD/MMC Commands and NOT just the  Read/Write Commands.
> or should I extend the mmc_test module present in kernel to support
> testing of individual commands as well ?

I would think the mmc_test module would be a good vehicle to extend to 
have it test individual commands.

Of course if there is no documentation or HOWTO use mmc_test module to 
test an individual MMC command then the work is kind-of for naught.

> Can I get some suggestions on what approach to take ?
>
>
> On Thu, Oct 20, 2011 at 12:48 PM, Arnd Bergmann<arnd@arndb.de>  wrote:
>>
>> On Thursday 20 October 2011 10:39:00 Shashidhar Hiremath wrote:
>>>    I am planning to use the existing IOCTL interface for SD/MMC present
>>> in the kernel.
>>>    Since, the IOCTL interface expects a read/write flag , and the MMC
>>> IOCTL is actually an interface to block layer I feel without modifying
>>> the block layer for the support of non-read write commands ,I may not
>>> be able to test the non-read/write commands through the IOCTL
>>> interface .
>>> Is there a way of doing this without modifying block layer ?
>>
>> Hi Shashidhar,
>>
>> I think there is actually no problem here at all. The block layer simply
>> passes the ioctl command number and argument to the driver, which can
>> do anything with it.
>>
>> What functionality are you actually looking for?
>>
>>         Arnd
>
>
>
> --
> regards,
> Shashidhar Hiremath
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


-- 
J (James/Jay) Freyensee
Storage Technology Group
Intel Corporation

  parent reply	other threads:[~2011-10-24 18:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-20  5:09 A question on IOCTL interface for MMC Shashidhar Hiremath
2011-10-20  7:18 ` Arnd Bergmann
2011-10-24 12:32   ` Shashidhar Hiremath
2011-10-24 16:39     ` Chris Ball
2011-10-24 18:28     ` J Freyensee [this message]
2011-11-17 15:46       ` Arnd Bergmann
2011-10-20 14:55 ` Andrei Warkentin
2011-10-21  4:34   ` Shashidhar Hiremath
2011-10-21 15:10     ` Shashidhar Hiremath
2011-10-21 15:01   ` OMAP HSMMC data timeout calculation Hebbar, Gururaja

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=4EA5AE64.2030106@linux.intel.com \
    --to=james_p_freyensee@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=cjb@laptop.org \
    --cc=john.calixto@modsystems.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=shashidharh@vayavyalabs.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.