From: Rob Herring <robh@kernel.org>
To: Zhenhua Huang <quic_zhenhuah@quicinc.com>
Cc: saravanak@google.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] of/address: Add error logging for of_match_bus() in address translation path
Date: Mon, 18 Aug 2025 11:49:07 -0500 [thread overview]
Message-ID: <20250818164907.GA1437284-robh@kernel.org> (raw)
In-Reply-To: <20250811095342.2383808-1-quic_zhenhuah@quicinc.com>
On Mon, Aug 11, 2025 at 05:53:42PM +0800, Zhenhua Huang wrote:
> The change introduced in
> commit 045b14ca5c36 ("of: WARN on deprecated #address-cells/#size-cells handling")
> triggers a warning on the direct ancestor node when translating properties
> like "iommu-addresses"/"reg". However, it fails to issue a warning if the
> ancestor’s ancestor is missing the required cells.
> For instance, if node_c lacks the necessary properties, no warning will be
> generated. Potential issues will be trigger further.
The point of the WARN is to only to check the immediate ancestor.
> node_c {
> //NO WARN
> node_b {
> //WARN on missing of "address-cells" and "size-cells"
> node_a {
> xxx = <memory_reion> //contains "iommu-addresses"
> }
> }
> }
Whether a warning is appropriate here depends on whether there's
'ranges' properties or not. If your schemas are complete, then they
should warn on missing 'ranges'. If ranges is present, then we should
get warnings if #address-cells or #size-cells is missing.
> Since of_match_bus() is now expected to succeed in traslation path,
now expected? Nothing changed in that aspect.
> routine __of_translate_address. Print an error message would help in
> identifying cases where it fails, making such issues easier to diagnose.
For errors in the DT (as opposed to errors using the API), it would be
better if we can check this at build time rather than run-time. And
generally I think we should already, but there could be some corner case
that we don't.
>
> Signed-off-by: Zhenhua Huang <quic_zhenhuah@quicinc.com>
> ---
> drivers/of/address.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/of/address.c b/drivers/of/address.c
> index f0f8f0dd191c..cd33ab64ccf3 100644
> --- a/drivers/of/address.c
> +++ b/drivers/of/address.c
> @@ -515,8 +515,10 @@ static u64 __of_translate_address(struct device_node *node,
> if (parent == NULL)
> return OF_BAD_ADDR;
> bus = of_match_bus(parent);
> - if (!bus)
> + if (!bus) {
> + pr_err("of_match_bus failed for device node(%pOF)\n", parent);
> return OF_BAD_ADDR;
> + }
>
> /* Count address cells & copy address locally */
> bus->count_cells(dev, &na, &ns);
> @@ -560,8 +562,10 @@ static u64 __of_translate_address(struct device_node *node,
>
> /* Get new parent bus and counts */
> pbus = of_match_bus(parent);
> - if (!pbus)
> + if (!pbus) {
> + pr_err("of_match_bus failed for device node(%pOF)\n", parent);
> return OF_BAD_ADDR;
If there's no case we expect of_match_bus() failing is correct
operation, then the error msg should be in the of_match_bus() function
rather than duplicated here. I'm not sure if there is any such case.
Rob
next prev parent reply other threads:[~2025-08-18 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 9:53 [PATCH] of/address: Add error logging for of_match_bus() in address translation path Zhenhua Huang
2025-08-18 16:49 ` Rob Herring [this message]
2025-08-19 3:56 ` Zhenhua Huang
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=20250818164907.GA1437284-robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_zhenhuah@quicinc.com \
--cc=saravanak@google.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.