[PATCH 2/4] imx6: refresh kernel config with 5.10 symbols

[Ilya Lipnitskiy]

Hi Petr,

On Sat, Feb 27, 2021 at 5:02 AM Petr Štetiar <ynezz at true.cz> wrote:
> +CONFIG_CRYPTO_ARCH_HAVE_LIB_CHACHA=y
>  CONFIG_CRYPTO_AUTHENC=y
>  CONFIG_CRYPTO_CBC=y
>  CONFIG_CRYPTO_CHACHA20=y
> @@ -117,12 +128,14 @@ CONFIG_CRYPTO_DRBG=y
>  CONFIG_CRYPTO_DRBG_HMAC=y
>  CONFIG_CRYPTO_DRBG_MENU=y
>  CONFIG_CRYPTO_ECB=y
> +CONFIG_CRYPTO_ENGINE=y
>  CONFIG_CRYPTO_HASH=y
>  CONFIG_CRYPTO_HASH2=y
>  CONFIG_CRYPTO_HASH_INFO=y
>  CONFIG_CRYPTO_HMAC=y
>  CONFIG_CRYPTO_HW=y
>  CONFIG_CRYPTO_JITTERENTROPY=y
> +CONFIG_CRYPTO_LIB_CHACHA_GENERIC=y
>  CONFIG_CRYPTO_LIB_DES=y
>  CONFIG_CRYPTO_LIB_SHA256=y
>  CONFIG_CRYPTO_LZO=y
> @@ -130,6 +143,7 @@ CONFIG_CRYPTO_MANAGER=y
>  CONFIG_CRYPTO_MANAGER2=y
>  CONFIG_CRYPTO_NULL=y
>  CONFIG_CRYPTO_NULL2=y
> +# CONFIG_CRYPTO_POLY1305_ARM is not set
>  CONFIG_CRYPTO_RNG=y
>  CONFIG_CRYPTO_RNG2=y
>  CONFIG_CRYPTO_RNG_DEFAULT=y
It seems that a lot of these CRYPTO symbols (at least ones that are
selected by kmod-crypto packages) should not be built into the kernel.
CHACHA and POLY libs in particular get selected by CONFIG_WIREGUARD
automatically. Seems like that's been happening for a long time on
this target though. Don't know if you want to clean it up here, just
my two cents.

Ilya