From: David Yang <mmyangfl@gmail.com>
To: linux-crypto@vger.kernel.org
Cc: David Yang <mmyangfl@gmail.com>,
Weili Qian <qianweili@huawei.com>,
Zhou Wang <wangzhou1@hisilicon.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/2] crypto: hisilicon - Add HiSilicon ADVCA Subsystem
Date: Tue, 6 Jun 2023 15:11:10 +0800 [thread overview]
Message-ID: <20230606071128.375567-1-mmyangfl@gmail.com> (raw)
HiSilicon ADVCA Subsystem contains various cryptographic devices, including
symmetric key ciphers, hash functions, RSA algorithms, as well as key
ladder and OTP memory.
This series adds symmetric key cipher and SHA algorithm family driver.
This series is based on Hi3798Mv100.
v2: sorry, I accidentally skipped v1.
v3:
* use devm_reset_control_get_optional_exclusive
* disable clocks if init failed
* put device reset when removal
* implement import function for sha device
* fix typo reported by test bot
v4: fix sparse warnings
David Yang (2):
crypto: hisilicon - Add HiSilicon ADVCA Subsystem
crypto: hisilicon/advca - Add SHA support
drivers/crypto/hisilicon/Kconfig | 11 +
drivers/crypto/hisilicon/Makefile | 1 +
drivers/crypto/hisilicon/advca/Makefile | 2 +
.../crypto/hisilicon/advca/hisi-advca-muc.c | 1530 +++++++++++++++++
.../crypto/hisilicon/advca/hisi-advca-sha.c | 659 +++++++
5 files changed, 2203 insertions(+)
create mode 100644 drivers/crypto/hisilicon/advca/Makefile
create mode 100644 drivers/crypto/hisilicon/advca/hisi-advca-muc.c
create mode 100644 drivers/crypto/hisilicon/advca/hisi-advca-sha.c
base-commit: f8dba31b0a826e691949cd4fdfa5c30defaac8c5
--
2.39.2
next reply other threads:[~2023-06-06 7:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 7:11 David Yang [this message]
2023-06-06 7:11 ` [PATCH v4 1/2] crypto: hisilicon - Add HiSilicon ADVCA Subsystem David Yang
2023-06-06 7:11 ` [PATCH v4 2/2] crypto: hisilicon/advca - Add SHA support David Yang
2023-06-16 10:58 ` 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=20230606071128.375567-1-mmyangfl@gmail.com \
--to=mmyangfl@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=qianweili@huawei.com \
--cc=wangzhou1@hisilicon.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