From: Felipe Balbi <balbi@kernel.org>
To: Marcus Folkesson <marcus.folkesson@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
davem@davemloft.net,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Ruslan Bilovol <ruslan.bilovol@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Kate Stewart <kstewart@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [v3,1/3] usb: gadget: ccid: add support for USB CCID Gadget Device
Date: Wed, 30 May 2018 15:28:18 +0300 [thread overview]
Message-ID: <87r2ltcopp.fsf@linux.intel.com> (raw)
Marcus Folkesson <marcus.folkesson@gmail.com> writes:
> Chip Card Interface Device (CCID) protocol is a USB protocol that
> allows a smartcard device to be connected to a computer via a card
> reader using a standard USB interface, without the need for each manufacturer
> of smartcards to provide its own reader or protocol.
>
> This gadget driver makes Linux show up as a CCID device to the host and let a
> userspace daemon act as the smartcard.
>
> This is useful when the Linux gadget itself should act as a cryptographic
> device or forward APDUs to an embedded smartcard device.
>
> Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
this could be done entirely in userspace with functionfs, why do we need
this part in the kernel? It does very little.
next reply other threads:[~2018-05-30 12:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 12:28 Felipe Balbi [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-10 18:46 [v3,1/3] usb: gadget: ccid: add support for USB CCID Gadget Device Marcus Folkesson
2018-06-22 16:48 Marcus Folkesson
2018-06-18 8:22 Felipe Balbi
2018-06-08 18:54 Marcus Folkesson
2018-05-30 14:04 Marcus Folkesson
2018-05-30 12:20 Greg Kroah-Hartman
2018-05-30 12:13 Marcus Folkesson
2018-05-30 11:30 Greg Kroah-Hartman
2018-05-30 11:24 Marcus Folkesson
2018-05-30 0:55 Andy Shevchenko
2018-05-29 18:50 Marcus Folkesson
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=87r2ltcopp.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marcus.folkesson@gmail.com \
--cc=mchehab+samsung@kernel.org \
--cc=rdunlap@infradead.org \
--cc=ruslan.bilovol@gmail.com \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).