From: Alan Cox <alan@linux.intel.com>
To: Juergen Beisert <jbe@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Jiri Slaby <jslaby@suse.cz>
Subject: Re: Driver for a SmartCard interface on a SoC
Date: Fri, 7 May 2010 14:02:48 +0100 [thread overview]
Message-ID: <20100507140248.7958da8f@linux.intel.com> (raw)
In-Reply-To: <201005071518.50406.jbe@pengutronix.de>
On Fri, 7 May 2010 15:18:50 +0200
Juergen Beisert <jbe@pengutronix.de> wrote:
> Hi,
>
> most SmartCard readers are external devices, connected via USB or
> serial lines. So, they do not need special in-kernel drivers.
>
> My SmartCard interface is part of a SoC (i.MX25 CPU). So, I need an
> in-kernel driver. Where would be the best place in the kernel tree,
> to add a driver for this kind of device? Maybe "drivers/char"?
> To exchange data with the plugged in SmartCard, only a couple of
> IOCTLs are required (detecting if a card is plugged in, socket power
> on/off, send reset to the card, configuring the communication
> parameters). Data exchange with the SmartCard can be done with simple
> read/write.
I'd say drivers/char if its a generic char device, but if its MX25
specific code entirely then drivers/platform or arch/.../platform.
The other question is one of API - it's going to best if the API isn't
MX25 specific but could reasonably be expected to work with other
future devices. A fake tty interface is probably overkill for that but
it would be good to get general review of any API.
next prev parent reply other threads:[~2010-05-07 13:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 13:18 Driver for a SmartCard interface on a SoC Juergen Beisert
2010-05-07 13:02 ` Alan Cox [this message]
2010-05-07 14:25 ` Juergen Beisert
2010-05-11 21:33 ` Alan Cox
2010-05-12 7:38 ` Juergen Beisert
2010-05-13 9:33 ` Alan Cox
2010-05-13 9:38 ` Alan Cox
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=20100507140248.7958da8f@linux.intel.com \
--to=alan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=jbe@pengutronix.de \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.