mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Tudor Ambarus <tudor.ambarus@microchip.com>
Cc: <alexandre.belloni@bootlin.com>,
	<ludovic.desroches@microchip.com>, <claudiu.beznea@microchip.com>,
	<dianders@chromium.org>, <emil.velikov@collabora.com>,
	<sam@ravnborg.org>, <codrin.ciubotariu@microchip.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] ARM: configs: at91: Enable crypto software implementations
Date: Fri, 17 Dec 2021 17:52:46 +0100	[thread overview]
Message-ID: <c161698a-8b18-8aa7-9f61-1f82cc2252ed@microchip.com> (raw)
In-Reply-To: <20211215134311.304427-1-tudor.ambarus@microchip.com>

On 15/12/2021 at 14:43, Tudor Ambarus wrote:
> Enable at least the same amount of algs as the hardware IPs are
> supporting so that they are able to fallback to the software
> implementations in case they need it.
> 
> Signed-off-by: Tudor Ambarus <tudor.ambarus@microchip.com>

Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>

And queued on at91-defconfig for 5.17.

Thanks, best regards,
   Nicolas


> ---
> v3: drop CONFIG_CRYPTO_MD5, as MD5 is not hw accelerated.
> 
> v2:
> - add CONFIG_CRYPTO_HMAC
> - update commit message
> - ignore other non-crypto changes that are revealed with
>    "make savedefconfig"
> 
>   arch/arm/configs/at91_dt_defconfig | 9 ++++++++-
>   arch/arm/configs/sama5_defconfig   | 8 ++++++++
>   2 files changed, 16 insertions(+), 1 deletion(-)
> 
> diff --git a/arch/arm/configs/at91_dt_defconfig b/arch/arm/configs/at91_dt_defconfig
> index a6310c8abcc3..549d01be0b47 100644
> --- a/arch/arm/configs/at91_dt_defconfig
> +++ b/arch/arm/configs/at91_dt_defconfig
> @@ -216,7 +216,14 @@ CONFIG_NLS_CODEPAGE_437=y
>   CONFIG_NLS_CODEPAGE_850=y
>   CONFIG_NLS_ISO8859_1=y
>   CONFIG_NLS_UTF8=y
> -CONFIG_CRYPTO_ECB=y
> +CONFIG_CRYPTO_CBC=y
> +CONFIG_CRYPTO_CFB=y
> +CONFIG_CRYPTO_OFB=y
> +CONFIG_CRYPTO_XTS=y
> +CONFIG_CRYPTO_HMAC=y
> +CONFIG_CRYPTO_SHA1=y
> +CONFIG_CRYPTO_SHA512=y
> +CONFIG_CRYPTO_DES=y
>   CONFIG_CRYPTO_USER_API_HASH=m
>   CONFIG_CRYPTO_USER_API_SKCIPHER=m
>   CONFIG_CRYPTO_DEV_ATMEL_AES=y
> diff --git a/arch/arm/configs/sama5_defconfig b/arch/arm/configs/sama5_defconfig
> index fe0d7ccc8fb2..03dd80c2a19e 100644
> --- a/arch/arm/configs/sama5_defconfig
> +++ b/arch/arm/configs/sama5_defconfig
> @@ -232,6 +232,14 @@ CONFIG_NLS_CODEPAGE_437=y
>   CONFIG_NLS_CODEPAGE_850=y
>   CONFIG_NLS_ISO8859_1=y
>   CONFIG_NLS_UTF8=y
> +CONFIG_CRYPTO_CBC=y
> +CONFIG_CRYPTO_CFB=y
> +CONFIG_CRYPTO_OFB=y
> +CONFIG_CRYPTO_XTS=y
> +CONFIG_CRYPTO_HMAC=y
> +CONFIG_CRYPTO_SHA1=y
> +CONFIG_CRYPTO_SHA512=y
> +CONFIG_CRYPTO_DES=y
>   CONFIG_CRYPTO_USER_API_HASH=m
>   CONFIG_CRYPTO_USER_API_SKCIPHER=m
>   CONFIG_CRYPTO_DEV_ATMEL_AES=y
> 


-- 
Nicolas Ferre

      reply	other threads:[~2021-12-17 16:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 13:43 Tudor Ambarus
2021-12-17 16:52 ` Nicolas Ferre [this message]

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=c161698a-8b18-8aa7-9f61-1f82cc2252ed@microchip.com \
    --to=nicolas.ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@microchip.com \
    --cc=codrin.ciubotariu@microchip.com \
    --cc=dianders@chromium.org \
    --cc=emil.velikov@collabora.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.desroches@microchip.com \
    --cc=sam@ravnborg.org \
    --cc=tudor.ambarus@microchip.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

all inboxes | Powered by JetHome®