rng: fix ARMv8.5 RNDR driver

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
the RNDR register already in the bind method.

For signaling the non-existence of a device the driver model requires using
ENOENT (and not ENODEV).

Fixes: 31565bb0aa2d ("driver: rng: Add DM_RNG interface for ARMv8.5 RNDR registers")
Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Tested-by: Andre Przywara <andre.przywara@arm.com>

diff --git a/drivers/rng/arm_rndr.c b/drivers/rng/arm_rndr.c
index 55989743eaee37a09cf61ad4ff7fbe9a64a8742c..4512330e68dfcc46a06e8c42be4315ed6557ec82 100644 (file)
--- a/drivers/rng/arm_rndr.c
+++ b/drivers/rng/arm_rndr.c
@@ -62,10 +62,10 @@ static const struct dm_rng_ops arm_rndr_ops = {
        .read = arm_rndr_read,
 };
 
-static int arm_rndr_probe(struct udevice *dev)
+static int arm_rndr_bind(struct udevice *dev)
 {
        if (!cpu_has_rndr())
-               return -ENODEV;
+               return -ENOENT;
 
        return 0;
 }
@@ -74,7 +74,7 @@ U_BOOT_DRIVER(arm_rndr) = {
        .name = DRIVER_NAME,
        .id = UCLASS_RNG,
        .ops = &arm_rndr_ops,
-       .probe = arm_rndr_probe,
+       .bind = arm_rndr_bind,
 };
 
 U_BOOT_DRVINFO(cpu_arm_rndr) = {