All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Cc: "Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
	linux-media@vger.kernel.org,
	"Sakari Ailus" <sakari.ailus@linux.intel.com>,
	"Jacopo Mondi" <jacopo+renesas@jmondi.org>,
	"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
	"Lad Prabhakar" <prabhakar.csengg@gmail.com>,
	linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 4/4] media: v4l2-async: Don't check fwnode name to detect endpoint
Date: Sun, 21 Jun 2020 02:04:40 +0300	[thread overview]
Message-ID: <20200620230440.GA20179@pendragon.ideasonboard.com> (raw)
In-Reply-To: <42d4269d-7498-b5f8-d966-86ecb75e7999@ideasonboard.com>

Hi Kieran,

On Wed, Mar 18, 2020 at 09:22:21AM +0000, Kieran Bingham wrote:
> On 18/03/2020 00:25, Laurent Pinchart wrote:
> > Use the presence of a "remote-endpoint" property to detect if a fwnode
> > is an endpoint node, as checking the node name won't work on ACPI-based
> > implementations.
> 
> Technically, won't this property only detect that the endpoint is
> connected to another endpoint, and 'un-connected' endpoints wont' match?
> 
> Of course in this instance - an unconnected endpoint is likely not much
> use and probably even shouldn't match ;-) ~(but it may still 'be' an
> endpoint).

Yes, technically speaking, this detects whether the node is an endpoint
and is connected. As you mentioned, there's little use in unconnected
endpoints here, as nobody would attempt to match them.

> Also - would this patch be squashed into 1/4?

I think that would make sense, yes. I'll do so in v3.

> I'll leave it to Sakari to comment on the actual validity of this
> approach all the same :-)

ACPI has a remote-endpoint property, but has no endpoint nodes. I wonder
what the remote-endpoint points to...

> > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> > ---
> >  drivers/media/v4l2-core/v4l2-async.c | 9 ++++-----
> >  1 file changed, 4 insertions(+), 5 deletions(-)
> > 
> > diff --git a/drivers/media/v4l2-core/v4l2-async.c b/drivers/media/v4l2-core/v4l2-async.c
> > index 9f393a7be455..a5f83ba502df 100644
> > --- a/drivers/media/v4l2-core/v4l2-async.c
> > +++ b/drivers/media/v4l2-core/v4l2-async.c
> > @@ -78,7 +78,6 @@ static bool match_fwnode(struct v4l2_async_notifier *notifier,
> >  	bool asd_fwnode_is_ep;
> >  	bool sd_fwnode_is_ep;
> >  	struct device *dev;
> > -	const char *name;
> >  
> >  	/*
> >  	 * Both the subdev and the async subdev can provide either an endpoint
> > @@ -92,10 +91,10 @@ static bool match_fwnode(struct v4l2_async_notifier *notifier,
> >  	 * Otherwise, check if the sd fwnode and the asd fwnode refer to an
> >  	 * endpoint or a device. If they're of the same type, there's no match.
> >  	 */
> > -	name = fwnode_get_name(sd->fwnode);
> > -	sd_fwnode_is_ep = name && strstarts(name, "endpoint");
> > -	name = fwnode_get_name(asd->match.fwnode);
> > -	asd_fwnode_is_ep = name && strstarts(name, "endpoint");
> > +	sd_fwnode_is_ep = fwnode_property_present(sd->fwnode,
> > +						  "remote-endpoint");
> > +	asd_fwnode_is_ep = fwnode_property_present(asd->match.fwnode,
> > +						   "remote-endpoint");
> >  
> >  	if (sd_fwnode_is_ep == asd_fwnode_is_ep)
> >  		return false;

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2020-06-20 23:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18  0:25 [PATCH v2 0/4] media: v4l2-async: Accept endpoints and devices for fwnode matching Laurent Pinchart
2020-03-18  0:25 ` [PATCH v2 1/4] " Laurent Pinchart
2020-03-18  0:25 ` [PATCH v2 2/4] media: v4l2-async: Pass notifier pointer to match functions Laurent Pinchart
2020-03-18  8:09   ` Sakari Ailus
2020-03-18  8:58   ` Kieran Bingham
2020-03-18  0:25 ` [PATCH v2 3/4] media: v4l2-async: Log message in case of heterogenous fwnode match Laurent Pinchart
2020-03-18  9:16   ` Kieran Bingham
2020-06-20 23:14     ` Laurent Pinchart
2020-03-18  9:16   ` Geert Uytterhoeven
2020-06-20 23:41     ` Laurent Pinchart
2020-03-18 14:03   ` Jacopo Mondi
2020-06-20 23:44     ` Laurent Pinchart
2020-03-18  0:25 ` [PATCH v2 4/4] media: v4l2-async: Don't check fwnode name to detect endpoint Laurent Pinchart
2020-03-18  9:22   ` Kieran Bingham
2020-06-20 23:04     ` Laurent Pinchart [this message]
2020-03-18 18:18 ` [PATCH v2 0/4] media: v4l2-async: Accept endpoints and devices for fwnode matching Lad, Prabhakar

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=20200620230440.GA20179@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=jacopo+renesas@jmondi.org \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=prabhakar.csengg@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.