From: David Gidson <david@gibson.dropbear.id.au>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: devicetree-compiler@vger.kernel.org,
Rob Herring <robh@kernel.org>,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH] checks: Fix detection of 'i2c-bus' node
Date: Thu, 10 Jul 2025 19:17:48 +1000 [thread overview]
Message-ID: <aG-FPE9rBRqhq70h@zatzit> (raw)
In-Reply-To: <20250709142452.249492-1-jonathanh@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]
On Wed, Jul 09, 2025 at 03:24:52PM +0100, Jon Hunter wrote:
> If an I2C controller has a 'i2c-bus' child node, then the function
> check_i2c_bus_bridge() does not detect this as expected and warnings
> such as the following are observed:
>
> Warning (i2c_bus_bridge): /example-0/i2c@7000c000: \
> incorrect #address-cells for I2C bus
> Warning (i2c_bus_bridge): /example-0/i2c@7000c000: \
> incorrect #size-cells for I2C bus
>
> These warnings occur because the '#address-cells' and '#size-cells' are
> not directly present under the I2C controller node but the 'i2c-bus'
> child node. The function check_i2c_bus_bridge() does not detect this
> because it is using the parent node's 'basenamelen' and not the child
> node's 'basenamelen' when comparing the child node name with 'i2c-bus'.
> The parent node's 'basenamelen' is shorter ('i2c') than 'i2c-bus' and so
> the strprefixeq() test fails. Fix this by using the child node
> 'basenamelen' when comparing the child node name.
>
> Fixes: 53a1bd546905 ("checks: add I2C bus checks")
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
Merged, thanks.
> ---
> checks.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/checks.c b/checks.c
> index 123f2eb425f4..7e3fed5005b3 100644
> --- a/checks.c
> +++ b/checks.c
> @@ -1024,7 +1024,7 @@ static void check_i2c_bus_bridge(struct check *c, struct dt_info *dti, struct no
> } else if (strprefixeq(node->name, node->basenamelen, "i2c")) {
> struct node *child;
> for_each_child(node, child) {
> - if (strprefixeq(child->name, node->basenamelen, "i2c-bus"))
> + if (strprefixeq(child->name, child->basenamelen, "i2c-bus"))
> return;
> }
> node->bus = &i2c_bus;
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-07-10 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 14:24 [PATCH] checks: Fix detection of 'i2c-bus' node Jon Hunter
2025-07-10 9:17 ` David Gidson [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=aG-FPE9rBRqhq70h@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=devicetree-compiler@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@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).