From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: devicetree@vger.kernel.org
Cc: linux-renesas-soc@vger.kernel.org
Subject: False positive warnings regarding phandle-arrays?
Date: Fri, 25 Sep 2026 22:38:31 +0200 [thread overview]
Message-ID: <arbbwj5z-YIVkfWL@shikoro> (raw)
[-- Attachment #1: Type: text/plain, Size: 1659 bytes --]
Hi all,
running dtb_checks with current Linux git and dt-schema git, I get this
warning:
DTC [C] arch/arm/boot/dts/renesas/r8a7790-lager.dtb
arch/arm/boot/dts/renesas/r8a7790-lager.dtb: i2c-mux1 (i2c-demux-pinctrl): i2c-parent:0: [99, 100] is too long
from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
arch/arm/boot/dts/renesas/r8a7790-lager.dtb: i2c-mux1 (i2c-demux-pinctrl): i2c-parent: [[99, 100]] is too short
from schema $id: http://devicetree.org/schemas/i2c/i2c-demux-pinctrl.yaml
(and a couple of more like this in i2c-demux nodes)
This is how "i2c-parent" is described in the YAML file:
i2c-parent:
$ref: /schemas/types.yaml#/definitions/phandle-array
minItems: 2
items:
maxItems: 1
description:
List of phandles of I2C masters available for selection. The first one
will be used as default.
where Rob added the constraints for the phandle-array with:
37534121c4e4 ("dt-bindings: Fix phandle-array constraints, again")
91f9a47ddb9d ("dt-bindings: i2c: mux: i2c-demux-pinctrl: Define "i2c-parent" constraints")
I think the DT describes it correctly:
i2cexio0: i2c-mux1 {
compatible = "i2c-demux-pinctrl";
i2c-parent = <&iic0>, <&i2c0>;
i2c-bus-name = "i2c-exio0";
#address-cells = <1>;
#size-cells = <0>;
};
Is this a false positive because the checker cannot distinguish between
two values with one cell and one value with two cells? I think a
potential fix belongs to the checker ideally, but maybe I am wrong and
need to annotate the DT?
Thank you for your help,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2026-09-25 20:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=arbbwj5z-YIVkfWL@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-renesas-soc@vger.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