From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: frieder.schrempf@kontron.de, laurent.pinchart@ideasonboard.com,
Tim Harvey <tharvey@gateworks.com>,
linux-arm-kernel@lists.infradead.org,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Javier Martinez Canillas <javierm@redhat.com>
Subject: [RFC 1/1] v4l: async: Add some debug prints
Date: Fri, 10 Feb 2023 00:16:34 +0200 [thread overview]
Message-ID: <20230209221634.35239-1-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <049f2fea-1725-74d9-d20d-fc4f7506d504@kontron.de>
Just add some debug prints for V4L2 async sub-device matching process. These
might come useful in figuring out why things don't work as expected.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
Frieder,
Can you try this? It prints what is being matched with what. Perhaps this
could be merged in a bit more refined form if it proves useful.
Not tested in any way.
drivers/media/v4l2-core/v4l2-async.c | 41 ++++++++++++++++++++++++----
1 file changed, 36 insertions(+), 5 deletions(-)
diff --git a/drivers/media/v4l2-core/v4l2-async.c b/drivers/media/v4l2-core/v4l2-async.c
index 2f1b718a9189..6c13a9488415 100644
--- a/drivers/media/v4l2-core/v4l2-async.c
+++ b/drivers/media/v4l2-core/v4l2-async.c
@@ -86,13 +86,18 @@ match_fwnode_one(struct v4l2_async_notifier *notifier,
bool sd_fwnode_is_ep;
struct device *dev;
+ dev_dbg(sd->dev, "async fwnode match %pfw vs. %pfw\n", sd_fwnode,
+ asd->match.fwnode);
+
/*
* Both the subdev and the async subdev can provide either an endpoint
* fwnode or a device fwnode. Start with the simple case of direct
* fwnode matching.
*/
- if (sd_fwnode == asd->match.fwnode)
+ if (sd_fwnode == asd->match.fwnode) {
+ dev_dbg(sd->dev, "true\n");
return true;
+ }
/*
* Otherwise, check if the sd fwnode and the asd fwnode refer to an
@@ -105,8 +110,12 @@ match_fwnode_one(struct v4l2_async_notifier *notifier,
sd_fwnode_is_ep = fwnode_graph_is_endpoint(sd_fwnode);
asd_fwnode_is_ep = fwnode_graph_is_endpoint(asd->match.fwnode);
- if (sd_fwnode_is_ep == asd_fwnode_is_ep)
+ dev_dbg(sd->dev, "async fwnode match %pfw vs. %pfw\n", sd_fwnode,
+ asd->match.fwnode);
+ if (sd_fwnode_is_ep == asd_fwnode_is_ep) {
+ dev_dbg(sd->dev, "unmatching node types (false)\n");
return false;
+ }
/*
* The sd and asd fwnodes are of different types. Get the device fwnode
@@ -120,10 +129,15 @@ match_fwnode_one(struct v4l2_async_notifier *notifier,
other_fwnode = sd_fwnode;
}
+ dev_dbg(sd->dev, "async fwnode (compat) match %pfw vs. %pfw\n",
+ dev_fwnode, other_fwnode);
+
fwnode_handle_put(dev_fwnode);
- if (dev_fwnode != other_fwnode)
+ if (dev_fwnode != other_fwnode) {
+ dev_dbg(sd->dev, "false\n");
return false;
+ }
/*
* We have a heterogeneous match. Retrieve the struct device of the side
@@ -143,6 +157,8 @@ match_fwnode_one(struct v4l2_async_notifier *notifier,
dev->driver->name);
}
+ dev_dbg(sd->dev, "true\n");
+
return true;
}
@@ -255,7 +271,10 @@ v4l2_async_nf_can_complete(struct v4l2_async_notifier *notifier)
v4l2_async_find_subdev_notifier(sd);
if (subdev_notifier &&
- !v4l2_async_nf_can_complete(subdev_notifier))
+ !v4l2_async_nf_can_complete(subdev_notifier)) {
+ if (subdev_notifier->sd)
+ deb_dbg(subdev_notifier->sd->dev,
+ "cannot complete\n");
return false;
}
@@ -273,18 +292,27 @@ v4l2_async_nf_try_complete(struct v4l2_async_notifier *notifier)
if (!list_empty(¬ifier->waiting))
return 0;
+ if (notifier->sd)
+ deb_dbg(notifier->sd->dev, "trying to complete\n");
+
/* Check the entire notifier tree; find the root notifier first. */
while (notifier->parent)
notifier = notifier->parent;
/* This is root if it has v4l2_dev. */
- if (!notifier->v4l2_dev)
+ if (!notifier->v4l2_dev) {
+ if (notifier->sd)
+ deb_dbg(notifier->sd->dev,
+ "V4L2 device not available\n");
return 0;
+ }
/* Is everything ready? */
if (!v4l2_async_nf_can_complete(notifier))
return 0;
+ deb_dbg(notifier->sd->dev, "complete\n");
+
return v4l2_async_nf_call_complete(notifier);
}
@@ -386,6 +414,9 @@ v4l2_async_nf_try_all_subdevs(struct v4l2_async_notifier *notifier)
continue;
ret = v4l2_async_match_notify(notifier, v4l2_dev, sd, asd);
+ deb_dbg(sd->dev, "bound to %s's notifier (ret %d)\n",
+ notifier->sd ? dev_name(notifier->sd->dev) : "no-dev",
+ ret);
if (ret < 0)
return ret;
--
2.30.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-09 22:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 14:24 Capture image from imx219 sensor on i.MX8MM Frieder Schrempf
2023-02-06 15:31 ` Laurent Pinchart
2023-02-06 15:38 ` Frieder Schrempf
2023-02-06 15:49 ` Dave Stevenson
2023-02-06 15:50 ` Laurent Pinchart
2023-02-07 15:24 ` Frieder Schrempf
2023-02-09 22:16 ` Sakari Ailus [this message]
2023-02-09 22:34 ` [RFC 1/1] v4l: async: Add some debug prints Laurent Pinchart
2023-02-15 12:00 ` Sakari Ailus
2023-02-15 19:23 ` Laurent Pinchart
2023-02-16 8:12 ` Sakari Ailus
2023-02-16 23:11 ` Laurent Pinchart
2023-02-17 11:39 ` Sakari Ailus
2023-02-14 10:25 ` Frieder Schrempf
2023-02-14 14:56 ` Sakari Ailus
2023-02-14 14:57 ` Frieder Schrempf
2023-02-09 22:19 ` Capture image from imx219 sensor on i.MX8MM Laurent Pinchart
2023-02-14 10:18 ` Frieder Schrempf
2023-02-14 10:52 ` Laurent Pinchart
2023-02-14 13:19 ` Frieder Schrempf
2023-02-14 13:57 ` Frieder Schrempf
2023-07-07 21:57 ` Tim Harvey
2023-07-10 7:57 ` Frieder Schrempf
2023-07-11 20:02 ` Tim Harvey
2023-07-12 6:27 ` Frieder Schrempf
2023-07-13 23:37 ` Tim Harvey
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=20230209221634.35239-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=frieder.schrempf@kontron.de \
--cc=javierm@redhat.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=tharvey@gateworks.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;
as well as URLs for NNTP newsgroup(s).