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: Tue, 11 May 2010 22:33:37 +0100 [thread overview]
Message-ID: <20100511223337.05945e68@linux.intel.com> (raw)
In-Reply-To: <201005071625.27872.jbe@pengutronix.de>
> > I'd say drivers/char if its a generic char device, but if its MX25
> > specific code entirely then drivers/platform or arch/.../platform.
>
> This driver covers a SmartCard core built into this kind of CPU. Its
> not like an interrupt controller which is specific to the CPU. Its a
> component like the USB and LCD controller, also built into this CPU.
> Maybe other CPUs will follow that are also using this SmartCard core
> (I don't know, only the manufacture knows).
The question is really about the interface as seen from userspace - is
that generic or could it be generic so you could write other card
drivers for different hardware to the same user space interface ?
> > 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.
>
> "faky tty"?
Some systems have before now implemented onchip smart card interfaces
with drivers that pretend to be a serial port talking a serial link to
the smartcard.
Alan
next prev parent reply other threads:[~2010-05-11 22:14 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
2010-05-07 14:25 ` Juergen Beisert
2010-05-11 21:33 ` Alan Cox [this message]
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=20100511223337.05945e68@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.