From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: linux-media@vger.kernel.org
Subject: Re: v4l2-async: regression due to endpoint matching
Date: Fri, 28 Apr 2023 08:24:22 +0200 [thread overview]
Message-ID: <5676976.irdbgypaU6@steina-w> (raw)
In-Reply-To: <43vsiiq5qvbmpnmcclh5jjemgkgym65iezvpbyu5y7sdrx63lq@v63zg7c7udyi>
Hi Jacopo,
Am Donnerstag, 27. April 2023, 18:01:38 CEST schrieb Jacopo Mondi:
> Hi Alexander
>
> On Thu, Apr 27, 2023 at 04:40:46PM +0200, Alexander Stein wrote:
> > Hi all,
> >
> > I have a setup on my TQMa6x (imx6q-mba6a.dts) with a tc358743 attached to
> > the MIPI CSI input.
> > I noticed that since commit 1f391df44607 ("media: v4l2-async: Use
> > endpoints in __v4l2_async_nf_add_fwnode_remote()") the async subdevice
> > probing does not work anymore. If I revert that, it is working again,
> > even on next-20230425.
> A similar issue has been discussed at
> https://www.spinics.net/lists/linux-media/msg223351.html
>
> Unfortunately there was no conclusion as far as I can tell if not that
> imx6 is now broken
Thanks for the link, seems like a non-trivial thing :(
From a glimpse, this series seems to deal with multiple async subdevs:
https://lore.kernel.org/all/20230330115853.1628216-1-sakari.ailus@linux.intel.com/
So imx-media-csi should be adjusted as well, no?
Best regards,
Alexander
> > $ cat /sys/kernel/debug/v4l2-async/pending_async_subdevices
> > imx-media:
> > ipu2_csi1:
> >
> > ipu2_csi0:
> > [fwnode] dev=21dc000.mipi,
> > node=/soc/bus@2100000/mipi@21dc000/port@3/endpoint>
> > ipu1_csi1:
> > [fwnode] dev=21dc000.mipi,
> > node=/soc/bus@2100000/mipi@21dc000/port@2/endpoint>
> > ipu1_csi0:
> > imx6-mipi-csi2:
> > ipu2_csi1_mux:
> >
> > ipu1_csi0_mux:
> > [fwnode] dev=21dc000.mipi,
> > node=/soc/bus@2100000/mipi@21dc000/port@1/endpoint>
> > With revert:
> > $ cat /sys/kernel/debug/v4l2-async/pending_async_subdevices
> > imx-media:
> > ipu2_csi1:
> > ipu2_csi0:
> > ipu1_csi1:
> > ipu1_csi0:
> > imx6-mipi-csi2:
> > ipu2_csi1_mux:
> > ipu1_csi0_mux:
> >
> > I also see these messages:
> > > video-mux 20e0000.iomuxc-gpr:ipu2_csi1_mux: Consider updating driver
> > > video-
> >
> > mux to match on endpoints
> >
> > > imx6-mipi-csi2 21dc000.mipi: Consider updating driver imx6-mipi-csi2 to
> >
> > match on endpoints
> >
> > > tc358743 0-000f: Consider updating driver tc358743 to match on endpoints
> > > video-mux 20e0000.iomuxc-gpr:ipu1_csi0_mux: Consider updating driver
> > > video-
> >
> > mux to match on endpoints
> >
> > But I'm unsure if this is related. As far as I can see match_fwnode_one
> > does match some nodes, but I do not know if they are the correct ones.
> > Anyone has an idea what's wrong here?
> >
> > Best regards,
> > Alexander
> > --
> > TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
> > Amtsgericht München, HRB 105018
> > Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
> > http://www.tq-group.com/
--
TQ-Systems GmbH | Mühlstraße 2, Gut Delling | 82229 Seefeld, Germany
Amtsgericht München, HRB 105018
Geschäftsführer: Detlef Schneider, Rüdiger Stahl, Stefan Schneider
http://www.tq-group.com/
next prev parent reply other threads:[~2023-04-28 6:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 14:40 v4l2-async: regression due to endpoint matching Alexander Stein
2023-04-27 16:01 ` Jacopo Mondi
2023-04-28 6:24 ` Alexander Stein [this message]
2023-04-28 6:31 ` Jacopo Mondi
2023-04-28 6:33 ` Alexander Stein
2023-04-28 6:43 ` Jacopo Mondi
2023-04-28 7:16 ` Sakari Ailus
2023-05-22 10:53 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 11:59 ` Sakari Ailus
2023-05-22 12:11 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 12:51 ` Sakari Ailus
2023-05-24 11:52 ` Thorsten Leemhuis
2023-05-25 7:23 ` Sakari Ailus
2023-04-28 6:52 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-06-26 11:41 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=5676976.irdbgypaU6@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=jacopo.mondi@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