From: Martin Cerveny <m.cerveny@computer.org>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: Martin Cerveny <m.cerveny@computer.org>,
Chen-Yu Tsai <wens@csie.org>,
"David S. Miller" <davem@davemloft.net>,
devicetree@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
Maxime Ripard <mripard@kernel.org>,
Rob Herring <robh+dt@kernel.org>
Subject: [PATCH v2 3/3] crypto: sun4i-ss - add the V3s variant of SS
Date: Mon, 31 Aug 2020 09:31:01 +0200 [thread overview]
Message-ID: <20200831073101.3608-4-m.cerveny@computer.org> (raw)
In-Reply-To: <20200831073101.3608-1-m.cerveny@computer.org>
Like A33 "sun4i-ss" has a difference, it give SHA1 digest
directly in BE. So add new compatible.
Tested-by: Martin Cerveny <m.cerveny@computer.org>
Signed-off-by: Martin Cerveny <m.cerveny@computer.org>
---
drivers/crypto/allwinner/sun4i-ss/sun4i-ss-core.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/crypto/allwinner/sun4i-ss/sun4i-ss-core.c b/drivers/crypto/allwinner/sun4i-ss/sun4i-ss-core.c
index a2b67f7f8..d24496cac 100644
--- a/drivers/crypto/allwinner/sun4i-ss/sun4i-ss-core.c
+++ b/drivers/crypto/allwinner/sun4i-ss/sun4i-ss-core.c
@@ -31,6 +31,10 @@ static const struct ss_variant ss_a33_variant = {
.sha1_in_be = true,
};
+static const struct ss_variant ss_v3s_variant = {
+ .sha1_in_be = true,
+};
+
static struct sun4i_ss_alg_template ss_algs[] = {
{ .type = CRYPTO_ALG_TYPE_AHASH,
.mode = SS_OP_MD5,
@@ -505,6 +509,9 @@ static const struct of_device_id a20ss_crypto_of_match_table[] = {
{ .compatible = "allwinner,sun8i-a33-crypto",
.data = &ss_a33_variant
},
+ { .compatible = "allwinner,sun8i-v3s-crypto",
+ .data = &ss_v3s_variant
+ },
{}
};
MODULE_DEVICE_TABLE(of, a20ss_crypto_of_match_table);
--
2.17.1
next prev parent reply other threads:[~2020-08-31 7:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 7:30 [PATCH v2 0/3] crypto: sun4i-ss: add support for V3s Martin Cerveny
2020-08-31 7:30 ` [PATCH v2 1/3] dt-bindings: crypto: add new compatible " Martin Cerveny
2020-09-01 9:32 ` Maxime Ripard
2020-09-01 10:57 ` Corentin Labbe
2020-09-01 11:40 ` Maxime Ripard
2020-09-02 6:28 ` Corentin Labbe
2020-09-05 15:51 ` Martin Cerveny
2020-09-14 18:24 ` Rob Herring
2020-08-31 7:31 ` [PATCH v2 2/3] ARM: dts: sun8i: v3s: Enable crypto engine Martin Cerveny
2020-09-01 9:33 ` Maxime Ripard
2020-08-31 7:31 ` Martin Cerveny [this message]
2020-08-31 11:50 ` [PATCH v2 3/3] crypto: sun4i-ss - add the V3s variant of SS Corentin Labbe
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=20200831073101.3608-4-m.cerveny@computer.org \
--to=m.cerveny@computer.org \
--cc=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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).