devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniele Alessandrelli <daniele.alessandrelli@linux.intel.com>
To: linux-crypto@vger.kernel.org,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>
Cc: devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Daniele Alessandrelli <daniele.alessandrelli@intel.com>,
	Mark Gross <mgross@linux.intel.com>
Subject: [PATCH 0/2] crypto: Add Keem Bay OCS AES/SM4 driver
Date: Thu, 26 Nov 2020 11:51:46 +0000	[thread overview]
Message-ID: <20201126115148.68039-1-daniele.alessandrelli@linux.intel.com> (raw)

The Intel Keem Bay SoC has an Offload Crypto Subsystem (OCS) featuring a
crypto engine for accelerating AES/SM4 operations.

This driver adds support for such hardware thus enabling hardware
acceleration for the following transformations on the Intel Keem Bay SoC:

- ecb(aes), cbc(aes), ctr(aes), cts(cbc(aes)), gcm(aes) and cbc(aes);
  supported for 128-bit and 256-bit keys.

- ecb(sm4), cbc(sm4), ctr(sm4), cts(cbc(sm4)), gcm(sm4) and cbc(sm4);
  supported for 128-bit keys.

The driver passes crypto manager self-tests, including the extra tests
(CRYPTO_MANAGER_EXTRA_TESTS=y).

Note: this driver is different from the Keem Bay OCS HCU driver previously
submitted. Keem Bay OCS HCU provides hardware-accelerated ahash, while
Keem Bay AES/SM4 (i.e., this driver) provides hardware-accelerated
skcipher and aead.


Daniele Alessandrelli (1):
  dt-bindings: Add Keem Bay OCS AES bindings

Mike Healy (1):
  crypto: keembay-ocs-aes: Add support for Keem Bay OCS AES/SM4

 .../crypto/intel,keembay-ocs-aes.yaml         |   45 +
 MAINTAINERS                                   |   10 +
 drivers/crypto/Kconfig                        |    2 +
 drivers/crypto/Makefile                       |    1 +
 drivers/crypto/keembay/Kconfig                |   39 +
 drivers/crypto/keembay/Makefile               |    5 +
 drivers/crypto/keembay/keembay-ocs-aes-core.c | 1713 +++++++++++++++++
 drivers/crypto/keembay/ocs-aes.c              | 1489 ++++++++++++++
 drivers/crypto/keembay/ocs-aes.h              |  129 ++
 9 files changed, 3433 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/crypto/intel,keembay-ocs-aes.yaml
 create mode 100644 drivers/crypto/keembay/Kconfig
 create mode 100644 drivers/crypto/keembay/Makefile
 create mode 100644 drivers/crypto/keembay/keembay-ocs-aes-core.c
 create mode 100644 drivers/crypto/keembay/ocs-aes.c
 create mode 100644 drivers/crypto/keembay/ocs-aes.h


base-commit: c3a98c3ad5c0dc60a1ac66bf91147a3f39cac96b
-- 
2.26.2


             reply	other threads:[~2020-11-26 11:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-26 11:51 Daniele Alessandrelli [this message]
2020-11-26 11:51 ` [PATCH 1/2] dt-bindings: Add Keem Bay OCS AES bindings Daniele Alessandrelli
2020-12-08 16:15   ` Rob Herring
2020-11-26 11:51 ` [PATCH 2/2] crypto: keembay-ocs-aes: Add support for Keem Bay OCS AES/SM4 Daniele Alessandrelli
2020-12-11 10:13 ` [PATCH 0/2] crypto: Add Keem Bay OCS AES/SM4 driver 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=20201126115148.68039-1-daniele.alessandrelli@linux.intel.com \
    --to=daniele.alessandrelli@linux.intel.com \
    --cc=daniele.alessandrelli@intel.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=mgross@linux.intel.com \
    --cc=robh+dt@kernel.org \
    /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).