linux-kernel - Re: Query related to MSR(Magnetic Stripe Reader) Device Driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 29 Jan 2013 05:33:46 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Priyaranjan Das <priyaranjan456789@...il.com>
Cc:	linux-kernel@...r.kernel.org, mankad.maulik@...il.com
Subject: Re: Query related to MSR(Magnetic Stripe Reader) Device Driver

On Mon, Jan 28, 2013 at 03:25:08PM +0530, Priyaranjan Das wrote:
> Hi Greg,
> 
> On Tue, Jan 22, 2013 at 10:06 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
> > On Tue, Jan 22, 2013 at 03:02:32PM +0530, Priyaranjan Das wrote:
> >> Hi All,
> >>
> >> I am working on MSR(Magnetic Stripe Reader) for a product . I wish to
> >> know whether any MSR( Magnetic Stripe/card Reader) driver is available
> >> in the current source or not. I need this for reference. Could anyone
> >> please help me?
> >
> > Most of these types of devices that I have worked with always show up as
> > a keyboard device (ps/2 pass-through or a USB hid device.)  What type of
> > interface does your device present to the operating system?
> >
> 
> The MSR will be a part of a SoC. It is  a memory mapped device hence
> there is no interface like USB.

Ok, that's different.  But how will your driver want to communicate the
reader data to userspace?  That will probably determine where you want
to put it.

I would recommend making it an input device and sending keystrokes that
you read from the card, so you can properly integrate into userspace
applications that are used to using a card reader.

> MSR IP contains an ADC which the driver will read and interpret the
> data. I am planning to write a Driver for the same. Will this driver
> fall under drivers/mfd/* ?

As per the above, I would think drivers/input/ wouldn't you?

Hope this helps,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/