Hi Fabio,
On 2021-09-21 13:08, Fabio Estevam wrote:
Hi Claudius,
On Mon, Sep 20, 2021 at 1:54 PM Claudius Heine <ch@xxxxxxx> wrote:
Here are the uevent entries without this RFC patch applied:
```
# udevadm info -q all -p devices/platform/soc@0/30800000.bus/30900000.crypto
P: /devices/platform/soc@0/30800000.bus/30900000.crypto
L: 0
E: DEVPATH=/devices/platform/soc@0/30800000.bus/30900000.crypto
E: DRIVER=caam
E: OF_NAME=crypto
E: OF_FULLNAME=/soc@0/bus@30800000/crypto@30900000
E: OF_COMPATIBLE_0=fsl,sec-v4.0
E: OF_COMPATIBLE_N=1
E: MODALIAS=of:NcryptoT(null)Cfsl,sec-v4.0
E: SUBSYSTEM=platform
E: USEC_INITIALIZED=4468986
E: ID_PATH=platform-30900000.crypto
E: ID_PATH_TAG=platform-30900000_crypto
Looking at the addresses above, it looks like you have a device from
the i.MX8M family.
caam module is being correctly autoloaded on imx8mn-evk, for example
on kernel 5.14.6:
https://storage.kernelci.org/stable/linux-5.14.y/v5.14.6/arm64/defconfig/gcc-8/lab-baylibre/baseline-imx8mn-ddr4-evk.html
It works on 5.10.67 too:
https://storage.kernelci.org/stable/linux-5.10.y/v5.10.67/arm64/defconfig/gcc-8/lab-baylibre/baseline-imx8mn-ddr4-evk.html
Which kernel version do you use?
I never have any issues with auto loading of the module. I just had an
issue where the rngd daemon didn't wait until the module was loaded and
failed to start. I found out that there was just some
`Wants=systemd-udev-settle.service` missing in the service file and then
everything worked. [1]
Marek just suspected at first that a `MODULE_ALIAS` might be necessary
in the driver and submitted this RFC patch for it.
So all is well from my end :) And thanks for everyone looking into this!
regards,
Claudius
[1] https://lists.openembedded.org/g/openembedded-core/message/156129
