From: Rob Herring <robh@kernel.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/2] of: base: Improve argument length mismatch error
Date: Fri, 7 Jan 2022 17:30:31 -0600 [thread overview]
Message-ID: <YdjNF1cEmgOl3ho5@robh.at.kernel.org> (raw)
In-Reply-To: <f6a68e0088a552ea9dfd4d8e3b5b586d92594738.1640881913.git.baruch@tkos.co.il>
On Thu, 30 Dec 2021 18:31:53 +0200, Baruch Siach wrote:
> The cells_name field of of_phandle_iterator might be NULL. Use the
> phandle name instead. With this change instead of:
>
> OF: /soc/pinctrl@1000000: (null) = 3 found 2
>
> We get:
>
> OF: /soc/pinctrl@1000000: phandle pinctrl@1000000 needs 3, found 2
>
> Which is a more helpful messages making DT debugging easier.
>
> In this particular example the phandle name looks like duplicate of the
> same node name. But note that the first node is the parent node
> (it->parent), while the second is the phandle target (it->node). They
> happen to be the same in the case that triggered this improvement. See
> commit 72cb4c48a46a ("arm64: dts: qcom: ipq6018: Fix gpio-ranges
> property").
>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> ---
> Note that commit 72cb4c48a46a mentioned above is currently in the
> arm64-for-5.17 branch of the qcom git tree.
>
> v2:
>
> Extend the commit log to explain the apparent node name duplication
> ---
> drivers/of/base.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
Applied, thanks!
next prev parent reply other threads:[~2022-01-07 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 16:31 [PATCH v2 1/2] of: base: Fix phandle argument length mismatch error message Baruch Siach
2021-12-30 16:31 ` [PATCH v2 2/2] of: base: Improve argument length mismatch error Baruch Siach
2022-01-07 23:30 ` Rob Herring [this message]
2022-01-07 23:29 ` [PATCH v2 1/2] of: base: Fix phandle argument length mismatch error message Rob Herring
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=YdjNF1cEmgOl3ho5@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=baruch@tkos.co.il \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=robh+dt@kernel.org \
/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).