Re: [meta-freescale] caam-keygen device not working for NXP imx7

On Mon, Jul 28, 2025 at 10:40=E2=80=AFAM tommy.beckmann via
lists.yoctoproject.org
<[email protected]> wrote:
>
> Dear Yocto Community,
>
> we struggle to setup the caam-keygen driver for NXP imx7 chip. The aim is=
 to create an encrypted part of the storage like it is done here: https://w=
ww.marcusfolkesson.se/blog/encrypted-storage-on-imx/.
>
> Therefore we activated the camm-keygen in the deconfig:
>
> zcat /proc/config.gz | grep -i caam
>
> CONFIG_TRUSTED_KEYS_CAAM=3Dy
> CONFIG_CRYPTO_DEV_FSL_CAAM_COMMON=3Dy
> CONFIG_CRYPTO_DEV_FSL_CAAM_CRYPTO_API_DESC=3Dy
> CONFIG_CRYPTO_DEV_FSL_CAAM_AHASH_API_DESC=3Dy
> CONFIG_CRYPTO_DEV_FSL_CAAM=3Dy
> # CONFIG_CRYPTO_DEV_FSL_CAAM_DEBUG is not set
> CONFIG_CRYPTO_DEV_FSL_CAAM_JR=3Dy
> CONFIG_CRYPTO_DEV_FSL_CAAM_RINGSIZE=3D9
> # CONFIG_CRYPTO_DEV_FSL_CAAM_INTC is not set
> CONFIG_CRYPTO_DEV_FSL_CAAM_CRYPTO_API=3Dy
> CONFIG_CRYPTO_DEV_FSL_CAAM_AHASH_API=3Dy
> CONFIG_CRYPTO_DEV_FSL_CAAM_PKC_API=3Dy
> CONFIG_CRYPTO_DEV_FSL_CAAM_RNG_API=3Dy
> CONFIG_CRYPTO_DEV_FSL_CAAM_PRNG_API=3Dy
> CONFIG_CRYPTO_DEV_FSL_CAAM_BLOB_GEN=3Dy
> # CONFIG_CRYPTO_DEV_FSL_CAAM_RNG_TEST is not set
>
> But when starting up the device registration is not complete:
>
>
> ~:# dmesg | grep caam
>
> [    1.544624] caam 30900000.crypto: device ID =3D 0x0a16030000000000 (Er=
a 8)
>
> [    1.551389] caam 30900000.crypto: job rings =3D 3, qi =3D 0
>
> [    1.560184] caam algorithms registered in /proc/crypto
>
> [    1.565593] caam 30900000.crypto: caam pkc algorithms registered in /p=
roc/crypto
>
> [    1.573038] caam 30900000.crypto: registering rng-caam
>
> [    1.578480] caam 30900000.crypto: rng crypto API alg registered prng-c=
aam
>
>
>
> Regarding NXP there should be an entry  =E2=80=9CDevice caam-keygen regis=
tered=E2=80=9D - but this is missing is missing?
>
>
> With the nxp kernel [linux-imx](https://github.com/nxp-imx/linux-imx) the=
 driver is working - but many other things does not work - that=C2=B4s why =
we aim to stay on meta-freescale.
>
> Is there support for the crypto drivers? Have we overseen something durin=
g activation?
meta-freescale provides recipes for 3 kernels:

linux-imx: use the same tag from NXP BSP (the link you shared)
linux-fslc: this points to the kernel.org linux, so it's upstream
linux-imx-fslc: the linux-imx from NXP BSP plus merge for stable tags
from kernel.org plus some patches the community decides it's needed
(sometimes it's backports, sometimes it's bugfixes)

> Do community support crypto drivers?
Yes, you can use the drivers provided by the source code.
Are the drivers tested? No (people do test and use, but the
meta-freescale community does not have a test environment)

> Have we overseen something during activation?
I personally haven't

We are more active on the GitHub PR/Issues, so I would recommend
submitting a GitHub Issue if you test the same in master or scarthgap.
And take a look in the current open issues to see the current work
from the community.

Daiane
>
> Thanks in advance and best regards,
> Tommy
>
> -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
> Links: You receive all messages sent to this group.
> View/Reply Online (#24972): https://lists.yoctoproject.org/g/meta-freesca=
le/message/24972
> Mute This Topic: https://lists.yoctoproject.org/mt/114413285/5992125
> Group Owner: [email protected]
> Unsubscribe: https://lists.yoctoproject.org/g/meta-freescale/unsub [daian=
[email protected]]
> -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
>