From: Arnd Bergmann <arnd@arndb.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Lubomir Rintel <lkundrak@v3.sk>,
linux-kernel@vger.kernel.org,
Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: [PATCH] char/pcmcia: add scr24x_cs chip card interface driver
Date: Mon, 10 Oct 2016 21:24:10 +0200 [thread overview]
Message-ID: <2290612.ZfX1KippBh@wuerfel> (raw)
In-Reply-To: <20161010173345.GA8476@kroah.com>
On Monday, October 10, 2016 7:33:45 PM CEST Greg Kroah-Hartman wrote:
> > +
> > +#define SCR24X_DEVS 8
> > +static DECLARE_BITMAP(scr24x_minors, SCR24X_DEVS);
> > +
> > +static struct class *scr24x_class;
> > +dev_t scr24x_devt;
>
> global variable? And why do you need a char device for this type of
> hardware? Isn't there already an existing interface for this device
> class?
It looks like this is modeled after the other two chip card drivers
in drivers/char/pcmcia/, which are also char devices. Looking at
https://pcsclite.alioth.debian.org/ccid.html, it seems that other
drivers for this protocol are typically in user space when they are
for USB devices, so apparently no existing subsystem abstraction
in the kernel.
This reminds me that there is just one other driver in drivers/char/pcmcia
(synclink_cs), and that should be moved to drivers/tty/ with the other
synclink variants. If we do this, we could rename drivers/char/pcmcia
to something that implies "smartcard".
Arnd
next prev parent reply other threads:[~2016-10-10 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 15:58 [PATCH] char/pcmcia: add scr24x_cs chip card interface driver Lubomir Rintel
2016-10-10 17:33 ` Greg Kroah-Hartman
2016-10-10 19:24 ` Arnd Bergmann [this message]
2016-10-16 9:23 ` Lubomir Rintel
2016-10-16 9:57 ` Greg Kroah-Hartman
2016-10-17 11:22 ` Lubomir Rintel
2016-10-17 11:34 ` Arnd Bergmann
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=2290612.ZfX1KippBh@wuerfel \
--to=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=lkundrak@v3.sk \
/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.