public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: J Freyensee <james_p_freyensee@linux.intel.com>
To: Shashidhar Hiremath <shashidharh@vayavyalabs.com>
Cc: cjb@laptop.org, Will Newton <will.newton@gmail.com>,
	Jae hoon Chung <jh80.chung@gmail.com>,
	James Hogan <james.hogan@imgtec.com>,
	kyungmin.park@samsung.com, linux-mmc@vger.kernel.org
Subject: Re: Testing Infrastructure for SD/MMC Commands
Date: Tue, 16 Aug 2011 09:03:56 -0700	[thread overview]
Message-ID: <4E4A94EC.7040606@linux.intel.com> (raw)
In-Reply-To: <CANYdXnrHWGPCeAEJQq6cmsZAyYfvvcSZ_1_3jKhcMbTARJpGVw@mail.gmail.com>

On 08/16/2011 02:26 AM, Shashidhar Hiremath wrote:
> adding mmc mailing list
>
> On Tue, Aug 16, 2011 at 11:12 AM, Shashidhar Hiremath
> <shashidharh@vayavyalabs.com>  wrote:
>> Hi All,
>>   i am planning to come up with a module that would help for testing
>> the SD/MMC controller to see if supports the particular command.
>>
>> For example ,Through this module , we will be able to see if a
>> particular command has been accepted by the device and whether device
>> has responded in the expected manner or not by checking its response.
>>
>> Can I get some points on how useful this infrastructure would be ,and
>> any inputs on what else  to cover under this ?
>>
>

It sounds like you are looking to design a functional model, a module 
that utilizes some type of design spec or standard to verify if the 
design implementation works according to the design-spec/standard, correct?

If true, my first question would be, what document will you be basing 
this module on?

It probably could be useful- the more testing on something the better. 
But I think the first step is you need to define what 
document/spec/standard this module is going to follow, then how this 
module is going to be designed and used, then go from there.

>
>


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

  reply	other threads:[~2011-08-16 16:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANYdXnoZK3OoWOnJhyq645GofnsXuk7tJm09Wv8=Y+gLujPSkQ@mail.gmail.com>
2011-08-16  9:26 ` Testing Infrastructure for SD/MMC Commands Shashidhar Hiremath
2011-08-16 16:03   ` J Freyensee [this message]
2011-08-16 16:11   ` Chris Ball
2011-08-17 13:51   ` seedshope
2011-08-17 14:11     ` about MicroSD transport issue for the current mainline kernel seedshope

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=4E4A94EC.7040606@linux.intel.com \
    --to=james_p_freyensee@linux.intel.com \
    --cc=cjb@laptop.org \
    --cc=james.hogan@imgtec.com \
    --cc=jh80.chung@gmail.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=shashidharh@vayavyalabs.com \
    --cc=will.newton@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