From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org
Cc: "Sakari Ailus" <sakari.ailus@iki.fi>,
"Jacopo Mondi" <jacopo@jmondi.org>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>
Subject: Re: [PATCH] media: v4l2-async: Use endpoints in __v4l2_async_nf_add_fwnode_remote()
Date: Sat, 09 Apr 2022 20:35:48 +0100 [thread overview]
Message-ID: <164953294830.22830.18350472818944012018@Monstersaurus> (raw)
In-Reply-To: <20220321145134.29820-1-laurent.pinchart@ideasonboard.com>
Quoting Laurent Pinchart (2022-03-21 14:51:34)
> From: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
>
> Matching on device fwnode handles is deprecated in favour of endpoint
> fwnode handles. Switch the __v4l2_async_nf_add_fwnode_remote() function
> to use the latter. The match code handles backward compatibility by
> falling by to the device fwnode handle, so this shouldn't introduce any
s/by/back/ ?
It sounds like this helps move other devices towards endpoint matching
more generically too, but I expect there will still be more specifics to
handle in receiver drivers?
And indeed the whole point of the fallback case was to make them
compatible... so:
Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
But I suspect this needs some testing on platforms that haven't yet
moved to endpoint matching.. ?
> regression.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> ---
> drivers/media/v4l2-core/v4l2-async.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/media/v4l2-core/v4l2-async.c b/drivers/media/v4l2-core/v4l2-async.c
> index 0404267f1ae4..67d7f445d429 100644
> --- a/drivers/media/v4l2-core/v4l2-async.c
> +++ b/drivers/media/v4l2-core/v4l2-async.c
> @@ -662,7 +662,7 @@ __v4l2_async_nf_add_fwnode_remote(struct v4l2_async_notifier *notif,
> struct v4l2_async_subdev *asd;
> struct fwnode_handle *remote;
>
> - remote = fwnode_graph_get_remote_port_parent(endpoint);
> + remote = fwnode_graph_get_remote_endpoint(endpoint);
> if (!remote)
> return ERR_PTR(-ENOTCONN);
>
> --
> Regards,
>
> Laurent Pinchart
>
next prev parent reply other threads:[~2022-04-09 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220922140658eucas1p29f9d609e795ed064e51694c0e7be80d3@eucas1p2.samsung.com>
2022-03-21 14:51 ` [PATCH] media: v4l2-async: Use endpoints in __v4l2_async_nf_add_fwnode_remote() Laurent Pinchart
2022-04-09 19:35 ` Kieran Bingham [this message]
2022-04-10 15:08 ` Laurent Pinchart
2022-09-22 14:06 ` Marek Szyprowski
2022-09-22 22:48 ` Sakari Ailus
2022-09-22 23:19 ` Daniel Scally
2022-09-23 9:27 ` Marek Szyprowski
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=164953294830.22830.18350472818944012018@Monstersaurus \
--to=kieran.bingham@ideasonboard.com \
--cc=jacopo@jmondi.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=sakari.ailus@iki.fi \
/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