From: Ludovic Desroches <ludovic.desroches@microchip.com>
To: linux-serial@vger.kernel.org, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Cc: gregkh@linuxfoundation.org, arnd@arndb.de,
richard.genoud@gmail.com, nicolas.ferre@microchip.com,
alexandre.belloni@bootlin.com, linux-kernel@vger.kernel.org,
Ludovic Desroches <ludovic.desroches@microchip.com>
Subject: [PATCH v5 0/2] add ISO7816 support
Date: Wed, 26 Sep 2018 14:58:46 +0200 [thread overview]
Message-ID: <20180926125848.31032-1-ludovic.desroches@microchip.com> (raw)
Hi,
This patchset adds support for the ISO7816 standard. The USART devices
in Microchip SoCs have an ISO7816 mode. It allows to let the USART
managing the CLK and I/O signals of a smart card.
Changes:
- v5
- rebase on tty-next.
- add documentation for the new ioctls (mimic rs485 one).
- fix a switch/case identation
- v4
- use the IP version number instead of the compatible string to set
min and max values for fidi.
- remove a useless macro for fidi.
- v3
- add IOCTLs to parisc arch.
- rework atmel_config_iso7816 according to the comments by Richard.
- keep max iteration hard coded. Will see later if the user need to
set this value. It may also concern the normal/inverse mode.
- improve the checking of the value from the user space.
- v2
- uart_get_iso7816_config: check there is an iso7816_config function.
- use IOCTL macros to generate the IOCTL number.
- check that reserved field is not used.
- remove debug logs.
- check that the iso7816_config is right before doing any action.
- change the error from nack and max iteration status to a debug
message.
- remove patch 3 as it concerns both rs485 and iso7816 to think more
about the need of adding a lock or not.
Nicolas Ferre (2):
tty/serial_core: add ISO7816 infrastructure
tty/serial: atmel: add ISO7816 support
Documentation/serial/serial-iso7816.txt | 83 ++++++++++++++
arch/alpha/include/uapi/asm/ioctls.h | 2 +
arch/mips/include/uapi/asm/ioctls.h | 2 +
arch/parisc/include/uapi/asm/ioctls.h | 2 +
arch/powerpc/include/uapi/asm/ioctls.h | 2 +
arch/sh/include/uapi/asm/ioctls.h | 2 +
arch/sparc/include/uapi/asm/ioctls.h | 2 +
arch/xtensa/include/uapi/asm/ioctls.h | 2 +
drivers/tty/serial/atmel_serial.c | 190 ++++++++++++++++++++++++++++++--
drivers/tty/serial/atmel_serial.h | 3 +-
drivers/tty/serial/serial_core.c | 60 ++++++++++
include/linux/serial_core.h | 3 +
include/uapi/asm-generic/ioctls.h | 2 +
include/uapi/linux/serial.h | 17 +++
14 files changed, 360 insertions(+), 12 deletions(-)
create mode 100644 Documentation/serial/serial-iso7816.txt
--
2.12.2
next reply other threads:[~2018-09-26 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-26 12:58 Ludovic Desroches [this message]
2018-09-26 12:58 ` [PATCH v5 0/2] add ISO7816 support Ludovic Desroches
2018-09-26 12:58 ` [PATCH v5 1/2] tty/serial_core: add ISO7816 infrastructure Ludovic Desroches
2018-09-26 12:58 ` Ludovic Desroches
2018-09-26 12:58 ` [PATCH v5 2/2] tty/serial: atmel: add ISO7816 support Ludovic Desroches
2018-09-26 12:58 ` Ludovic Desroches
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=20180926125848.31032-1-ludovic.desroches@microchip.com \
--to=ludovic.desroches@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=richard.genoud@gmail.com \
/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).