Dear Tom, The following changes since commit c5e461fbf7cc72f0c1c8a79226b6a5170e56cb4d:
Merge tag 'u-boot-imx-master-20240108' of https://gitlab.denx.de/u-boot/custodians/u-boot-imx (2024-01-08 13:39:43 -0500) are available in the Git repository at: https://source.denx.de/u-boot/custodians/u-boot-efi.git tags/rng-2024-04-rc1 for you to fetch changes up to 1351cd3b4b1b18cafa4893a44378ca6b1d091c8e: rng: detect RISC-V Zkr RNG device in bind method (2024-01-09 07:37:05 +0100) Gitlab CI showed no issues: https://source.denx.de/u-boot/custodians/u-boot-efi/-/pipelines/19241 ---------------------------------------------------------------- Pull request rng-2024-04-rc1 QEMU does not provide information in the device-tree if the ARMv8.5 RNDR or the RISC-V Zkr RNG have been enabled on the command line. In different parts of our code we assume that the first RNG device is the one to be used. Therefore it is preferable to detect the availability of said devices already in the bind method. There has been a related discussion if the U_BOOT_DRVINFO() macro should be used for architectural devices (https://lore.kernel.org/u-boot/20231031125552.26698-1-heinrich.schucha...@canonical.com/). This aspect is not touched by this series. ---------------------------------------------------------------- Heinrich Schuchardt (2): rng: fix ARMv8.5 RNDR driver rng: detect RISC-V Zkr RNG device in bind method drivers/rng/arm_rndr.c | 6 +++--- drivers/rng/riscv_zkr_rng.c | 34 ++++++++++++++++++++++++++-------- 2 files changed, 29 insertions(+), 11 deletions(-)
