From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: kieran.bingham@ideasonboard.com
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Kieran Bingham" <kbingham@kernel.org>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"open list:MEDIA DRIVERS FOR RENESAS - FCP"
<linux-renesas-soc@vger.kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"Sakari Ailus" <sakari.ailus@iki.fi>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Frank Rowand" <frowand.list@gmail.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE"
<devicetree@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/3] of: base: Provide of_graph_get_port_parent()
Date: Thu, 18 May 2017 16:18:39 +0300 [thread overview]
Message-ID: <2172554.nJqIiczhoI@avalon> (raw)
In-Reply-To: <61138419-5781-bbec-7ac5-44524ad501ce@ideasonboard.com>
Hi Kieran,
On Wednesday 17 May 2017 21:02:42 Kieran Bingham wrote:
> On 17/05/17 17:36, Rob Herring wrote:
> > On Wed, May 17, 2017 at 10:03 AM, Kieran Bingham wrote:
> >> From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> >>
> >> When handling endpoints, the v4l2 async framework needs to identify the
> >> parent device of a port endpoint.
> >>
> >> Adapt the existing of_graph_get_remote_port_parent() such that a caller
> >> can obtain the parent of a port without parsing the remote-endpoint
> >> first.
> >
> > A similar patch is already applied as part of the ASoC graph card support.
> >
> > Rob
>
> Ah yes, a quick google finds it...
>
> : https://patchwork.kernel.org/patch/9658907/
>
> Surprisingly similar patch ... and a familiar name.
Very similar indeed, down to identical problems ;-) Quoting your patch,
> /**
> + * of_graph_get_port_parent() - get port's parent node
> + * @node: pointer to a local endpoint device_node
> + *
> + * Return: device node associated with endpoint @node.
> + * Use of_node_put() on it when done.
> + */
The documentation of the return value is a bit confusing to me. I assume that,
by device node, you meant the DT node corresponding to the device of the
endpoint which is passed as an argument. However, device node cal also refer
to struct device_node. Should this be clarified ?
> Morimoto-san - you beat me to it :D !
>
> Thanks Rob, (And Morimoto!)
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2017-05-18 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.6800d0e1b9b578b82f68dec1b99b3a601d6e54ca.1495032810.git-series.kieran.bingham+renesas@ideasonboard.com>
2017-05-17 15:03 ` [PATCH v1 1/3] of: base: Provide of_graph_get_port_parent() Kieran Bingham
[not found] ` <56c9c74fa9e2879aea9e008d54d8b8d7b450b8ae.1495032810.git-series.kieran.bingham+renesas-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2017-05-17 16:36 ` Rob Herring
[not found] ` <CAL_JsqLvXH3kKV-DxWuNrAYGh8=L8Mdg5zcm2RsHZTpmi_8g-g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-05-17 20:02 ` Kieran Bingham
[not found] ` <61138419-5781-bbec-7ac5-44524ad501ce-ryLnwIuWjnjg/C1BVhZhaw@public.gmane.org>
2017-05-17 23:53 ` Kuninori Morimoto
2017-05-18 13:18 ` Laurent Pinchart [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=2172554.nJqIiczhoI@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=kbingham@kernel.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).