From: Antoine Tenart <atenart@kernel.org>
To: Aleksander Jan Bajkowski <olek2@wp.pl>
Cc: naseefkm@gmail.com, cjd@cjdns.fr, ansuelsmth@gmail.com,
atenart@kernel.org, herbert@gondor.apana.org.au,
davem@davemloft.net, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crypto: inside-secure/eip93 - make it selectable for ECONET
Date: Mon, 23 Mar 2026 09:27:18 +0100 [thread overview]
Message-ID: <acD5Sdd6w63ixSsD@kwain> (raw)
In-Reply-To: <20260320211931.829476-1-olek2@wp.pl>
On Fri, Mar 20, 2026 at 10:19:23PM +0100, Aleksander Jan Bajkowski wrote:
> Econet SoCs feature an integrated EIP93 in revision 3.0p1. It is identical
> to the one used by the Airoha AN7581 and the MediaTek MT7621. Ahmed reports
> that the EN7528 passes testmgr's self-tests. This driver should also work
> on other little endian Econet SoCs.
>
> CC: Ahmed Naseef <naseefkm@gmail.com>
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
Reviewed-by: Antoine Tenart <atenart@kernel.org>
Thanks!
> ---
> drivers/crypto/inside-secure/eip93/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/crypto/inside-secure/eip93/Kconfig b/drivers/crypto/inside-secure/eip93/Kconfig
> index 8353d3d7ec9b..29523f6927dd 100644
> --- a/drivers/crypto/inside-secure/eip93/Kconfig
> +++ b/drivers/crypto/inside-secure/eip93/Kconfig
> @@ -1,7 +1,7 @@
> # SPDX-License-Identifier: GPL-2.0
> config CRYPTO_DEV_EIP93
> tristate "Support for EIP93 crypto HW accelerators"
> - depends on SOC_MT7621 || ARCH_AIROHA ||COMPILE_TEST
> + depends on SOC_MT7621 || ARCH_AIROHA || ECONET || COMPILE_TEST
> select CRYPTO_LIB_AES
> select CRYPTO_LIB_DES
> select CRYPTO_SKCIPHER
> --
> 2.51.0
>
next prev parent reply other threads:[~2026-03-23 8:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 21:19 [PATCH] crypto: inside-secure/eip93 - make it selectable for ECONET Aleksander Jan Bajkowski
2026-03-23 8:27 ` Antoine Tenart [this message]
2026-03-23 9:19 ` Ahmed Naseef
2026-03-27 10:09 ` 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=acD5Sdd6w63ixSsD@kwain \
--to=atenart@kernel.org \
--cc=ansuelsmth@gmail.com \
--cc=cjd@cjdns.fr \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=naseefkm@gmail.com \
--cc=olek2@wp.pl \
/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