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:	Fri, 15 Feb 2013 18:28:24 +0100
From:	Lars-Peter Clausen <lars@...afoo.de>
To:	Priyaranjan Das <priyaranjan456789@...il.com>
CC:	Greg KH <gregkh@...uxfoundation.org>, linux-iio@...r.kernel.org,
	linux-kernel@...r.kernel.org, mankad.maulik@...il.com
Subject: Re: Query related to MSR(Magnetic Stripe Reader) Device Driver

On 02/15/2013 12:18 PM, Priyaranjan Das wrote:
> Hi Greg,
> 
> On Thu, Jan 31, 2013 at 11:09 AM, Priyaranjan Das
> <priyaranjan456789@...il.com> wrote:
>> Hi Greg,
>>
>> On Tue, Jan 29, 2013 at 7:03 PM, Greg KH <gregkh@...uxfoundation.org> wrote:
>>> 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,
>>>
>>
>> Thanks for your help!.
>>
>> Yes, you are right, it should be under drivers/input.
>> I am trying to prepare the design right now.
>>
>>
> 
> The MSR IP can be also be used either as a general purpose ADC or in
> Magnetic stripe card reader mode.The IP supports both the modes and
> provides FIFO for storing ADC data.
> 
> I also got to know about IIO subsystem where  ADC drivers are
> implemented. Our use-case will be to use either Magnetic Stripe reader
> mode or general purpose ADC mode in a given configuration. Can I use
> IIO subsystem for the Magnetic Stripe driver?

Hi,

Well for the ADC functionality it certainly makes sense to use the IIO
framework. The magnetic stripe reader functionality should probably go into
drivers/input. How to do this exactly depends a bit on how exactly the
hardware works. A good idea is probably to use a mfd driver which
instantiates both the input and the IIO driver and does some arbitration
between them. If the magnetic stripe reader is a feature that's build on top
of the ADC functionality you could use the IIO in-kernel API to do ADC
conversions from your input driver. If the ADC and magnetic stripe reader
mode are exclusive-or it probably makes sense to only instantiate one of
them at a time from the MFD driver.

- Lars

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ