linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Németh Márton" <nm127@freemail.hu>
To: Greg KH <gregkh@suse.de>
Cc: Chris Ball <cjb@laptop.org>,
	linux-mmc@vger.kernel.org, devel@driverdev.osuosl.org,
	techeng <dzshen@gmail.com>,
	clyu@citiz.net, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add Winbond WB528SD Secure Digital (SD) card reader driver
Date: Sat, 21 Jan 2012 15:54:13 +0100	[thread overview]
Message-ID: <4F1AD195.70305@freemail.hu> (raw)
In-Reply-To: <20120121125153.GB18829@suse.de>

Hi Greg,

thanks for your response and your questions, I think it will help my
work very much.

Greg KH wrote:
> On Sat, Jan 21, 2012 at 11:52:37AM +0100, Németh Márton wrote:
>> From: Márton Németh <nm127@freemail.hu>
>>
>> This driver version of Winbond WB528SD can detect mechanical card
>> presence only. The information is provided through sysfs.
> 
> How is it provided through sysfs?  Is this done in a standard way?  If
> not, why not?

I used device_create_file()/device_remove_file() and DEVICE_ATTR(), in
that sense it is standard. I'm not sure, however, that you a referring
to this, rather referring to the standard way how other SD card readers
provide the card presence information to the user space, right?
To tell you the truth, I could not find an other PCI card driver which
I can take as an example, I would need some help on this.

> Why is this driver submitted to the staging tree?  What is keeping it
> from going into the "real" portion of the kernel for other card readers?

Interrupt handling, read, write and connecting the driver upwards to the
block subsystem, I guess.

> We need a TODO file for what is needed to get it moved out of staging.

I can create one, no problem.

> Oh, and it needs to do a bit more than just detect a card to be useful,
> right?  How about read/write to it?

Sure. My intention was to get feedback for my work as early as possible.
I reached a state where a minimal level of functionality is available:
the mechanical SD card presence is available for userspace programs.

The read/write access will be a bit more difficult, I guess because I
currently don't have access to the register programming reference of
this device, I can use the trial-and-error method, for example.

	Márton Németh

  reply	other threads:[~2012-01-21 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-21 10:52 [PATCH] Add Winbond WB528SD Secure Digital (SD) card reader driver Németh Márton
2012-01-21 12:51 ` Greg KH
2012-01-21 14:54   ` Németh Márton [this message]
2012-01-21 15:02     ` Greg KH

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=4F1AD195.70305@freemail.hu \
    --to=nm127@freemail.hu \
    --cc=cjb@laptop.org \
    --cc=clyu@citiz.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=dzshen@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).