From: Corentin Labbe <clabbe.montjoie@gmail.com> To: davem@davemloft.net, herbert@gondor.apana.org.au, mark.rutland@arm.com, mripard@kernel.org, robh+dt@kernel.org, wens@csie.org Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com, Corentin Labbe <clabbe.montjoie@gmail.com> Subject: [PATCH v2 0/3] crypto: sun4i-ss: fix SHA1 on A33 SecuritySystem Date: Wed, 20 Nov 2019 16:28:30 +0100 [thread overview] Message-ID: <20191120152833.20443-1-clabbe.montjoie@gmail.com> (raw) Thanks to Igor Pecovnik, I have now in my kernelCI lab, a sun8i-a33-olinuxino. Strange behavour, crypto selftests was failling but only for SHA1 on this A33 SoC. This is due to the A33 SS having a difference with all other SS, it give SHA1 digest directly in BE. This serie handle this difference. Changes since v1: - removed compatible fallback Corentin Labbe (3): dt-bindings: crypto: add new compatible for A33 SS ARM: dts: sun8i: a33: add the new SS compatible crypto: sun4i-ss: add the A33 variant of SS .../crypto/allwinner,sun4i-a10-crypto.yaml | 2 ++ arch/arm/boot/dts/sun8i-a33.dtsi | 2 +- .../crypto/allwinner/sun4i-ss/sun4i-ss-core.c | 22 ++++++++++++++++++- .../crypto/allwinner/sun4i-ss/sun4i-ss-hash.c | 5 ++++- drivers/crypto/allwinner/sun4i-ss/sun4i-ss.h | 9 ++++++++ 5 files changed, 37 insertions(+), 3 deletions(-) -- 2.23.0
WARNING: multiple messages have this Message-ID (diff)
From: Corentin Labbe <clabbe.montjoie@gmail.com> To: davem@davemloft.net, herbert@gondor.apana.org.au, mark.rutland@arm.com, mripard@kernel.org, robh+dt@kernel.org, wens@csie.org Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com, Corentin Labbe <clabbe.montjoie@gmail.com>, linux-crypto@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 0/3] crypto: sun4i-ss: fix SHA1 on A33 SecuritySystem Date: Wed, 20 Nov 2019 16:28:30 +0100 [thread overview] Message-ID: <20191120152833.20443-1-clabbe.montjoie@gmail.com> (raw) Thanks to Igor Pecovnik, I have now in my kernelCI lab, a sun8i-a33-olinuxino. Strange behavour, crypto selftests was failling but only for SHA1 on this A33 SoC. This is due to the A33 SS having a difference with all other SS, it give SHA1 digest directly in BE. This serie handle this difference. Changes since v1: - removed compatible fallback Corentin Labbe (3): dt-bindings: crypto: add new compatible for A33 SS ARM: dts: sun8i: a33: add the new SS compatible crypto: sun4i-ss: add the A33 variant of SS .../crypto/allwinner,sun4i-a10-crypto.yaml | 2 ++ arch/arm/boot/dts/sun8i-a33.dtsi | 2 +- .../crypto/allwinner/sun4i-ss/sun4i-ss-core.c | 22 ++++++++++++++++++- .../crypto/allwinner/sun4i-ss/sun4i-ss-hash.c | 5 ++++- drivers/crypto/allwinner/sun4i-ss/sun4i-ss.h | 9 ++++++++ 5 files changed, 37 insertions(+), 3 deletions(-) -- 2.23.0 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-11-20 15:28 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-20 15:28 Corentin Labbe [this message] 2019-11-20 15:28 ` [PATCH v2 0/3] crypto: sun4i-ss: fix SHA1 on A33 SecuritySystem Corentin Labbe 2019-11-20 15:28 ` [PATCH v2 1/3] dt-bindings: crypto: add new compatible for A33 SS Corentin Labbe 2019-11-20 15:28 ` Corentin Labbe 2019-12-04 16:18 ` Rob Herring 2019-12-04 16:18 ` Rob Herring 2019-11-20 15:28 ` [PATCH v2 2/3] ARM: dts: sun8i: a33: add the new SS compatible Corentin Labbe 2019-11-20 15:28 ` Corentin Labbe 2019-11-20 15:28 ` [PATCH v2 3/3] crypto: sun4i-ss: add the A33 variant of SS Corentin Labbe 2019-11-20 15:28 ` Corentin Labbe 2019-11-22 12:53 ` Maxime Ripard 2019-11-22 12:53 ` Maxime Ripard 2019-12-11 9:35 ` Herbert Xu 2019-12-11 9:35 ` Herbert Xu 2020-03-12 5:39 ` [linux-sunxi] [PATCH v2 0/3] crypto: sun4i-ss: fix SHA1 on A33 SecuritySystem Chen-Yu Tsai 2020-03-12 5:39 ` Chen-Yu Tsai
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=20191120152833.20443-1-clabbe.montjoie@gmail.com \ --to=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=linux-sunxi@googlegroups.com \ --cc=mark.rutland@arm.com \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.