linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tudor Ambarus <tudor.ambarus@microchip.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net
Cc: linux-crypto@vger.kernel.org, wsa@the-dreams.de,
	linux-i2c@vger.kernel.org, nicolas.ferre@microchip.com,
	Tudor Ambarus <tudor.ambarus@microchip.com>
Subject: [PATCH 0/3] crypto: introduce Microchip / Atmel ECC driver
Date: Wed, 5 Jul 2017 13:07:57 +0300	[thread overview]
Message-ID: <1499249280-31779-1-git-send-email-tudor.ambarus@microchip.com> (raw)

Hi,

This patch set introduces Microchip / Atmel ECC driver.

The first patch adds some helpers that will be used by fallbacks to
kpp software implementations.

The second patch adds ECDH support for the ATECC508A (I2C)
cryptographic engine. The I2C interface is designed to operate
at a maximum clock speed of 1MHz.

The device features hardware acceleration for the NIST standard
P256 prime curve and supports the complete key life cycle from
private key generation to ECDH key agreement.

Random private key generation is supported internally within
the device to ensure that the private key can never be known
outside of the device. If the user wants to use its own private
keys, the driver will fallback to the ecdh software implementation.

Tudor Ambarus (3):
  crypto: kpp: add get/set_flags helpers
  crypto: introduce Microchip / Atmel ECC driver
  MAINTAINERS: add a maintainer for Microchip / Atmel ECC driver

 .../devicetree/bindings/crypto/atmel-crypto.txt    |  13 +
 MAINTAINERS                                        |   6 +
 drivers/crypto/Kconfig                             |  14 +
 drivers/crypto/Makefile                            |   1 +
 drivers/crypto/atmel-ecc.c                         | 781 +++++++++++++++++++++
 drivers/crypto/atmel-ecc.h                         | 128 ++++
 include/crypto/kpp.h                               |  10 +
 7 files changed, 953 insertions(+)
 create mode 100644 drivers/crypto/atmel-ecc.c
 create mode 100644 drivers/crypto/atmel-ecc.h

-- 
2.7.4

             reply	other threads:[~2017-07-05 10:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 10:07 Tudor Ambarus [this message]
2017-07-05 10:07 ` [PATCH 1/3] crypto: kpp: add get/set_flags helpers Tudor Ambarus
2017-07-05 10:07 ` [PATCH 2/3] crypto: introduce Microchip / Atmel ECC driver Tudor Ambarus
2017-07-05 10:08 ` [PATCH 3/3] MAINTAINERS: add a maintainer for " Tudor Ambarus
2017-07-05 10:54 ` [PATCH 0/3] crypto: introduce " Marcel Holtmann
2017-07-05 11:44   ` Tudor Ambarus
2017-07-05 12:26     ` Marcel Holtmann
2017-07-18 10:38 ` Herbert Xu

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=1499249280-31779-1-git-send-email-tudor.ambarus@microchip.com \
    --to=tudor.ambarus@microchip.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=wsa@the-dreams.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).