public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hansg@kernel.org>
To: Daniel Scally <djrscally@gmail.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Hans de Goede <hansg@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>
Subject: [PATCH 3/4] media: ov8865: Improve error logging when fwnode is not found
Date: Mon, 23 Jun 2025 13:00:34 +0200	[thread overview]
Message-ID: <20250623110035.18340-4-hansg@kernel.org> (raw)
In-Reply-To: <20250623110035.18340-1-hansg@kernel.org>

From: Hans de Goede <hdegoede@redhat.com>

The ov8865 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.952061] i2c i2c-INT347A: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

Signed-off-by: Hans de Goede <hdegoede@redhat.com>
---
 drivers/media/i2c/ov8865.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/media/i2c/ov8865.c b/drivers/media/i2c/ov8865.c
index 95ffe7536aa6..a2138f7988aa 100644
--- a/drivers/media/i2c/ov8865.c
+++ b/drivers/media/i2c/ov8865.c
@@ -2991,7 +2991,8 @@ static int ov8865_probe(struct i2c_client *client)
 
 	handle = fwnode_graph_get_next_endpoint(dev_fwnode(dev), NULL);
 	if (!handle)
-		return -EPROBE_DEFER;
+		return dev_err_probe(dev, -EPROBE_DEFER,
+				     "waiting for fwnode graph endpoint\n");
 
 	sensor->endpoint.bus_type = V4L2_MBUS_CSI2_DPHY;
 
-- 
2.49.0


  parent reply	other threads:[~2025-06-23 11:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23 11:00 [PATCH 0/4] media: i2c/pci: Various error logging improvements Hans de Goede
2025-06-23 11:00 ` [PATCH 1/4] media: ov5693: Improve error logging when fwnode is not found Hans de Goede
2025-06-24 12:43   ` Daniel Scally
2025-06-23 11:00 ` [PATCH 2/4] media: ov7251: " Hans de Goede
2025-06-24 12:44   ` Daniel Scally
2025-06-23 11:00 ` Hans de Goede [this message]
2025-06-24 12:44   ` [PATCH 3/4] media: ov8865: " Daniel Scally
2025-06-23 11:00 ` [PATCH 4/4] media: ipu-bridge: Improve error logging when waiting for IVSC to become ready Hans de Goede
2025-06-24 12:44   ` Daniel Scally
  -- strict thread matches above, loose matches on Subject: below --
2024-10-05 12:15 [PATCH 1/4] media: ov5693: Improve error logging when fwnode is not found Hans de Goede
2024-10-05 12:15 ` [PATCH 3/4] media: ov8865: " Hans de Goede

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250623110035.18340-4-hansg@kernel.org \
    --to=hansg@kernel.org \
    --cc=djrscally@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox