media: ov5693: Improve error logging when fwnode is not found

The ov5693 driver waits for the endpoint fwnode to show up in case this
fwnode is created by a bridge-driver.

It does this by returning -EPROBE_DEFER, but it does not use
dev_err_probe() so no reason for deferring gets registered.

After 30 seconds the kernel logs a warning that the probe is still
deferred, which looks like this:

[   33.951709] i2c i2c-INT33BE:00: deferred probe pending: (reason unknown)

Use dev_err_probe() when returning -EPROBE_DEFER to register the probe
deferral reason changing the error to:

deferred probe pending: waiting for fwnode graph endpoint

Also update the comment to not refer to the no longer existing cio2-bridge
code.

Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Signed-off-by: Hans Verkuil <hverkuil@xs4all.nl>

diff --git a/drivers/media/i2c/ov5693.c b/drivers/media/i2c/ov5693.c
index 46b9ce1116763297d63c6d919c6f3dc2ce768ff1..485efd15257e091f5c445dcb34cda0ba99f5fd31 100644 (file)
--- a/drivers/media/i2c/ov5693.c
+++ b/drivers/media/i2c/ov5693.c
@@ -1222,9 +1222,14 @@ static int ov5693_check_hwcfg(struct ov5693_device *ov5693)
        unsigned int i;
        int ret;
 
+       /*
+        * Sometimes the fwnode graph is initialized by the bridge driver
+        * Bridge drivers doing this may also add GPIO mappings, wait for this.
+        */
        endpoint = fwnode_graph_get_next_endpoint(fwnode, NULL);
        if (!endpoint)
-               return -EPROBE_DEFER; /* Could be provided by cio2-bridge */
+               return dev_err_probe(ov5693->dev, -EPROBE_DEFER,
+                                    "waiting for fwnode graph endpoint\n");
 
        ret = v4l2_fwnode_endpoint_alloc_parse(endpoint, &bus_cfg);
        fwnode_handle_put(endpoint);