From: Philipp Zabel <p.zabel@pengutronix.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, kernel@pengutronix.de,
Francesco Dolcini <francesco@dolcini.it>
Subject: Re: [PATCH] media: v4l2-async: fix binding async subdevs with multiple source ports
Date: Mon, 16 Jan 2023 14:46:07 +0100 [thread overview]
Message-ID: <20230116134607.GA31026@pengutronix.de> (raw)
In-Reply-To: <Y8Sji3VUaPvKprCF@pendragon.ideasonboard.com>
Hi Laurent,
On Mon, Jan 16, 2023 at 03:08:27AM +0200, Laurent Pinchart wrote:
[...]
> To make sure I understand this correctly, you need both changes, with
> the change in __v4l2_async_nf_has_async_subdev() meant to address asds
> being added after the subdev has been registered, and the change in
> v4l2_async_register_subdev() meant to address asds that have been added
> before ?
Yes, your understanding is correct.
> The imx6 ipu drivers implement a "clever hack" to handle the
> multi-endpoint issue that was never officially supported by v4l2-async.
That belongs in parentheses all right. I think it might even have been
accidental.
> Obviously, as it has worked so far, leaving it broken isn't a very nice
> option. The fix feels a bit like a hack though, and a better solution
> would be to allow subdevs to be matched multiple times, by multiple
> consumers. That's a more intrusive change though, so I could be OK with
> this as a short term fix, assuming it doesn't break anything else.
Right, the intention was that this patch could be applied on stable
kernels, as I only had noticed the issue after the release.
> I would however want to ensure this doesn't get abused by new drivers.
> Could we add a dev_warn() somewhere to indicate that multi-endpoint
> matching is not supported and shouldn't be used until fixed ? Sakari,
> what do you think ?
[...]
pr_warn_once() in both places, perhaps?
regards
Philipp
next prev parent reply other threads:[~2023-01-16 13:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 10:48 [PATCH] media: v4l2-async: fix binding async subdevs with multiple source ports Philipp Zabel
2023-01-13 11:24 ` Philipp Zabel
2023-01-16 1:08 ` Laurent Pinchart
2023-01-16 11:57 ` Francesco Dolcini
2023-01-16 13:46 ` Philipp Zabel [this message]
2023-01-16 16:09 ` Laurent Pinchart
2023-01-16 13:27 ` Sakari Ailus
2023-01-17 13:16 ` Sakari Ailus
2023-01-17 13:29 ` Laurent Pinchart
2023-01-18 13:14 ` Aishwarya Kothari
2023-01-20 16:33 ` Philipp Zabel
2023-01-26 8:32 ` Aishwarya Kothari
2023-02-15 10:10 ` Sakari Ailus
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=20230116134607.GA31026@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=francesco@dolcini.it \
--cc=kernel@pengutronix.de \
--cc=laurent.pinchart@ideasonboard.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