From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Ezequiel Garcia <ezequiel@collabora.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>,
kernel@collabora.com
Subject: Re: [PATCH v2] media: v4l2-async: Add waiting subdevices debugfs
Date: Tue, 5 Jan 2021 16:20:04 +0200 [thread overview]
Message-ID: <20210105142004.GR11878@paasikivi.fi.intel.com> (raw)
In-Reply-To: <ba227fd79a0e0921b68365a4d636926b7c8b14ef.camel@collabora.com>
Hi Ezequiel,
On Tue, Jan 05, 2021 at 10:34:14AM -0300, Ezequiel Garcia wrote:
> Hi Sakari, Laurent,
>
> On Tue, 2021-01-05 at 05:46 +0200, Laurent Pinchart wrote:
> > Hi Ezequiel,
> >
> > Thank you for the patch.
> >
> > On Mon, Jan 04, 2021 at 02:48:40PM -0300, Ezequiel Garcia wrote:
> > > There is currently little to none information available
> > > about the reasons why a v4l2-async device hasn't
> > > probed completely.
> > >
> > > Inspired by the "devices_deferred" debugfs file,
> > > add a file to list information about the subdevices
> > > that are on waiting lists, for each notifier.
> > >
> > > This is useful to debug v4l2-async subdevices
> > > and notifiers, for instance when doing device bring-up.
> > >
> > > For instance, a typical output would be:
> > >
> > > $ cat /sys/kernel/debug/video4linux/pending_async_subdevices
> > > ipu1_csi1:
> > > [fwnode] dev=20e0000.iomuxc-gpr:ipu1_csi1_mux, node=/soc/bus@2000000/iomuxc-gpr@20e0000/ipu1_csi1_mux
> > > ipu1_csi0:
> > > [fwnode] dev=20e0000.iomuxc-gpr:ipu1_csi0_mux, node=/soc/bus@2000000/iomuxc-gpr@20e0000/ipu1_csi0_mux
> > > imx6-mipi-csi2:
> > > [fwnode] dev=1-003c, node=/soc/bus@2100000/i2c@21a4000/camera@3c
> > > imx-media:
> > >
> > > Note that match-type "custom" prints no information.
> > > Since there are no in-tree users of this match-type,
> > > the implementation doesn't bother.
> >
> > I wonder if we should drop it.
> >
>
> That would make sense, unless we have some out-of-tree
> users, and we want to support that.
>
> Sakari, what do you think?
I think we could drop it. But I'd do that in a separate patch from this
one.
--
Regards,
Sakari Ailus
prev parent reply other threads:[~2021-01-05 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 17:48 [PATCH v2] media: v4l2-async: Add waiting subdevices debugfs Ezequiel Garcia
2021-01-05 0:20 ` Sakari Ailus
2021-01-07 20:58 ` Ezequiel Garcia
2021-01-07 21:12 ` Laurent Pinchart
2021-01-07 22:08 ` Sakari Ailus
2021-01-05 3:46 ` Laurent Pinchart
2021-01-05 13:34 ` Ezequiel Garcia
2021-01-05 14:20 ` Sakari Ailus [this message]
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=20210105142004.GR11878@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=ezequiel@collabora.com \
--cc=hverkuil@xs4all.nl \
--cc=kernel@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
/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