linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gilad Ben-Yossef <gilad@benyossef.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>
Cc: Ofir Drang <Ofir.Drang@arm.com>,
	Yael Chemla <Yael.Chemla@arm.com>,
	linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] crypto: ccree: add CryptoCell 713 baseline support
Date: Mon, 29 Oct 2018 09:50:11 +0000	[thread overview]
Message-ID: <1540806616-5483-1-git-send-email-gilad@benyossef.com> (raw)

Add first batch of patches for support of Arm TrustZone CryptoCell 713.

Changes from v1:
- Format dt bindings document one version per line and correct the heading
  as indicated by Rob Herring.

Gilad Ben-Yossef (3):
  crypto: ccree: add support for CryptoCell 713
  dt-bindings: crypto: ccree: add ccree 713
  crypto: ccree: add SM4 support

 .../devicetree/bindings/crypto/arm-cryptocell.txt  |  7 ++-
 drivers/crypto/Kconfig                             |  3 +-
 drivers/crypto/ccree/cc_cipher.c                   | 66 ++++++++++++++++++++++
 drivers/crypto/ccree/cc_driver.c                   | 23 +++++---
 drivers/crypto/ccree/cc_driver.h                   |  5 +-
 drivers/crypto/ccree/cc_hw_queue_defs.h            |  3 +
 6 files changed, 94 insertions(+), 13 deletions(-)

-- 
2.7.4


             reply	other threads:[~2018-10-29  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-29  9:50 Gilad Ben-Yossef [this message]
2018-10-29  9:50 ` [PATCH v2 1/3] crypto: ccree: add support for CryptoCell 713 Gilad Ben-Yossef
2018-10-29  9:50 ` [PATCH v2 2/3] dt-bindings: crypto: ccree: add ccree 713 Gilad Ben-Yossef
2018-10-30 22:20   ` Rob Herring
2018-10-29  9:50 ` [PATCH v2 3/3] crypto: ccree: add SM4 support Gilad Ben-Yossef
2018-11-09  9:50 ` [PATCH v2 0/3] crypto: ccree: add CryptoCell 713 baseline support 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=1540806616-5483-1-git-send-email-gilad@benyossef.com \
    --to=gilad@benyossef.com \
    --cc=Ofir.Drang@arm.com \
    --cc=Yael.Chemla@arm.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.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).