From: Herbert Xu <herbert@gondor.apana.org.au>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Linus Walleij <linus.walleij@linaro.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v2 0/6] crypto - wire up Atmel SHA204A as RNG in DT and ACPI mode
Date: Thu, 30 May 2019 21:44:05 +0800 [thread overview]
Message-ID: <20190530134404.kpxdpkxbzyxhpbxo@gondor.apana.org.au> (raw)
In-Reply-To: <20190524162651.28189-1-ard.biesheuvel@linaro.org>
On Fri, May 24, 2019 at 06:26:45PM +0200, Ard Biesheuvel wrote:
> The Socionext SynQuacer based 96boards DeveloperBox platform does not
> incorporate a random number generator, but it does have a 96boards low
> speed connector which supports extension boards such as the Secure96,
> which has a TPM and some crypto accelerators, one of which incorporates
> a random number generator.
>
> This series implements support for the RNG part, which is one of several
> functions of the Atmel SHA204A I2C crypto accelerator, and wires it up so
> both DT and ACPI based boot methods can use the device.
>
> v2:
> - update DT binding patches so the SHA204A and ECC508A module bindings are
> in trivial-devices.yaml.
> - add acks from Linus and Mika
>
> Assuming Rob is ok now with the DT binding patches, can we please take
> this through the crypto tree?
>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: Tudor Ambarus <tudor.ambarus@microchip.com>
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
>
> Ard Biesheuvel (6):
> i2c: acpi: permit bus speed to be discovered after enumeration
> crypto: atmel-ecc: add support for ACPI probing on non-AT91 platforms
> crypto: atmel-ecc: factor out code that can be shared
> crypto: atmel-i2c: add support for SHA204A random number generator
> dt-bindings: add Atmel SHA204A I2C crypto processor
> dt-bindings: move Atmel ECC508A I2C crypto processor to
> trivial-devices
>
> Documentation/devicetree/bindings/crypto/atmel-crypto.txt | 13 -
> Documentation/devicetree/bindings/trivial-devices.yaml | 4 +
> drivers/crypto/Kconfig | 19 +-
> drivers/crypto/Makefile | 2 +
> drivers/crypto/atmel-ecc.c | 403 ++------------------
> drivers/crypto/atmel-ecc.h | 116 ------
> drivers/crypto/atmel-i2c.c | 364 ++++++++++++++++++
> drivers/crypto/atmel-i2c.h | 196 ++++++++++
> drivers/crypto/atmel-sha204a.c | 171 +++++++++
> drivers/i2c/i2c-core-acpi.c | 6 +-
> 10 files changed, 781 insertions(+), 513 deletions(-)
> delete mode 100644 drivers/crypto/atmel-ecc.h
> create mode 100644 drivers/crypto/atmel-i2c.c
> create mode 100644 drivers/crypto/atmel-i2c.h
> create mode 100644 drivers/crypto/atmel-sha204a.c
All applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2019-05-30 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 16:26 [PATCH v2 0/6] crypto - wire up Atmel SHA204A as RNG in DT and ACPI mode Ard Biesheuvel
2019-05-24 16:26 ` [PATCH v2 1/6] i2c: acpi: permit bus speed to be discovered after enumeration Ard Biesheuvel
2019-05-24 16:26 ` [PATCH v2 2/6] crypto: atmel-ecc: add support for ACPI probing on non-AT91 platforms Ard Biesheuvel
2019-05-24 21:52 ` Linus Walleij
2019-05-24 16:26 ` [PATCH v2 3/6] crypto: atmel-ecc: factor out code that can be shared Ard Biesheuvel
2019-05-24 16:26 ` [PATCH v2 4/6] crypto: atmel-i2c: add support for SHA204A random number generator Ard Biesheuvel
2019-05-24 16:26 ` [PATCH v2 5/6] dt-bindings: add Atmel SHA204A I2C crypto processor Ard Biesheuvel
2019-05-24 19:42 ` Rob Herring
2019-05-24 16:26 ` [PATCH v2 6/6] dt-bindings: move Atmel ECC508A I2C crypto processor to trivial-devices Ard Biesheuvel
2019-05-24 19:43 ` Rob Herring
2019-05-30 13:44 ` Herbert Xu [this message]
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=20190530134404.kpxdpkxbzyxhpbxo@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=ard.biesheuvel@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=tudor.ambarus@microchip.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).