From: Dmitry Osipenko <digetx@gmail.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>, Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/6] of_graph: add of_graph_get_local_port()
Date: Tue, 16 Jun 2020 16:56:41 +0300 [thread overview]
Message-ID: <8b7c6395-edd8-cecd-7004-e9f3f22d61f2@gmail.com> (raw)
In-Reply-To: <20200616012513.GF1629@pendragon.ideasonboard.com>
16.06.2020 04:25, Laurent Pinchart пишет:
> On Tue, Jun 16, 2020 at 04:21:12AM +0300, Laurent Pinchart wrote:
>> Hi Dmitry,
>>
>> Thank you for the patch.
>>
>> On Sun, Jun 14, 2020 at 08:22:29PM +0300, Dmitry Osipenko wrote:
>>> In some case, like a DRM display code for example, it's useful to silently
>>> check whether port node exists at all in a device-tree before proceeding
>>> with parsing the graph.
>>>
>>> This patch adds of_graph_get_local_port() which returns pointer to a local
>>> port node, or NULL if graph isn't specified in a device-tree for a given
>>> device node.
>>>
>>> Reviewed-by: Rob Herring <robh@kernel.org>
>>> Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
>>> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
>>> ---
>>> drivers/of/property.c | 32 +++++++++++++++++++++++---------
>>> include/linux/of_graph.h | 7 +++++++
>>> 2 files changed, 30 insertions(+), 9 deletions(-)
>>>
>>> diff --git a/drivers/of/property.c b/drivers/of/property.c
>>> index 1f2086f4e7ce..05c5f619b8bb 100644
>>> --- a/drivers/of/property.c
>>> +++ b/drivers/of/property.c
>>> @@ -608,15 +608,7 @@ struct device_node *of_graph_get_next_endpoint(const struct device_node *parent,
>>> * parent port node.
>>> */
>>> if (!prev) {
>>> - struct device_node *node;
>>> -
>>> - node = of_get_child_by_name(parent, "ports");
>>> - if (node)
>>> - parent = node;
>>> -
>>> - port = of_get_child_by_name(parent, "port");
>>> - of_node_put(node);
>>> -
>>> + port = of_graph_get_local_port(parent);
>>> if (!port) {
>>> pr_err("graph: no port node found in %pOF\n", parent);
>>> return NULL;
>>> @@ -765,6 +757,28 @@ struct device_node *of_graph_get_remote_port(const struct device_node *node)
>>> }
>>> EXPORT_SYMBOL(of_graph_get_remote_port);
>>>
>>> +/**
>>> + * of_graph_get_local_port() - get local port node
>>> + * @node: pointer to a local endpoint device_node
>>> + *
>>> + * Return: First local port node associated with local endpoint node linked
>>> + * to @node. Use of_node_put() on it when done.
>>> + */
>>> +struct device_node *of_graph_get_local_port(const struct device_node *node)
>
> I forgot to mention that, given that there could be multiple 'port'
> nodes, this function would be better named
> of_graph_get_first_local_port(). 'first' here would refer to the nodes
> order in the device tree, which I believe may not match the port number.
> For instance, in the following case
>
> ports {
> #address-cells = <1>;
> #size-cells = <1>;
> port@1 {
> reg = <1>;
> };
> port@0 {
> reg = <0>;
> };
> };
>
> the function would I believe return port@1. It may be a good idea to
> explain this in the documentation.
Hello Laurent,
It's correct that the port@1 will be returned in yours example.
I'll improve the doc and the function's name in the next revision, thank
you for the suggestions!
> Depending on how you use this
> function, if your only use case is to test for the presence of port
> nodes, it may be best to return a bool and name it of_graph_has_port()
> or something similar.
>
>>> +{
>>> + struct device_node *ports, *port;
>>> +
>>> + ports = of_get_child_by_name(node, "ports");
>>> + if (ports)
>>> + node = ports;
>>> +
>>> + port = of_get_child_by_name(node, "port");
>>> + of_node_put(ports);
>>> +
>>> + return port;
>>
>> The implementation doesn't seem to match the documentation. If node is a
>> pointer to an endpoint, it should not have any ports child.
Right, I'll reword the doc in v8. This function doesn't differentiate
between start / end points. It's up to a user of this function to check
whether node is endpoint or something else if needed.
Thank you very much for the comments!
next prev parent reply other threads:[~2020-06-16 13:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 17:22 [PATCH v7 0/6] Support DRM bridges on NVIDIA Tegra Dmitry Osipenko
2020-06-14 17:22 ` [PATCH v7 1/6] of_graph: add of_graph_get_local_port() Dmitry Osipenko
2020-06-16 1:21 ` Laurent Pinchart
2020-06-16 1:25 ` Laurent Pinchart
2020-06-16 13:56 ` Dmitry Osipenko [this message]
2020-06-16 14:14 ` Dmitry Osipenko
2020-06-14 17:22 ` [PATCH v7 2/6] drm/of: Make drm_of_find_panel_or_bridge() to check graph's presence Dmitry Osipenko
2020-06-16 1:26 ` Laurent Pinchart
2020-06-16 14:42 ` Dmitry Osipenko
2020-06-14 17:22 ` [PATCH v7 3/6] drm/tegra: output: Don't leak OF node on error Dmitry Osipenko
2020-06-14 17:22 ` [PATCH v7 4/6] drm/tegra: output: Support DRM bridges Dmitry Osipenko
2020-06-14 17:22 ` [PATCH v7 5/6] drm/tegra: output: rgb: Support LVDS encoder bridge Dmitry Osipenko
2020-06-14 17:22 ` [PATCH v7 6/6] drm/tegra: output: rgb: Wrap directly-connected panel into DRM bridge Dmitry Osipenko
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=8b7c6395-edd8-cecd-7004-e9f3f22d61f2@gmail.com \
--to=digetx@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=frowand.list@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).