From: "Rob Herring (Arm)" <robh@kernel.org>
To: Abdurrahman Hussain <abdurrahman@nexthop.ai>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Peter Rosin <peda@lysator.liu.se>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
devicetree@vger.kernel.org, Andi Shyti <andi.shyti@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: i2c: convert i2c-mux-reg to DT schema
Date: Sun, 07 Jun 2026 11:32:35 -0500 [thread overview]
Message-ID: <178084995520.4043722.11073475733919673696.robh@kernel.org> (raw)
In-Reply-To: <20260607-i2c-mux-reg-base-bus-num-v1-1-f193b5a8fedc@nexthop.ai>
On Sun, 07 Jun 2026 01:20:55 -0700, Abdurrahman Hussain wrote:
> Convert Documentation/devicetree/bindings/i2c/i2c-mux-reg.txt to
> the YAML schema so the i2c-mux-reg binding is validated by
> dt_binding_check.
>
> Also document a new optional "base-bus-num" property: when
> present, child adapter N is registered as Linux i2c bus number
> (base-bus-num + reg), so static references such as sensors.conf
> stanzas remain stable across boots. The matching driver support is
> added in the following patch.
>
> Signed-off-by: Abdurrahman Hussain <abdurrahman@nexthop.ai>
> ---
> .../devicetree/bindings/i2c/i2c-mux-reg.txt | 74 --------------
> .../devicetree/bindings/i2c/i2c-mux-reg.yaml | 110 +++++++++++++++++++++
> 2 files changed, 110 insertions(+), 74 deletions(-)
>
My bot found errors running 'make dt_binding_check' on your patch:
yamllint warnings/errors:
dtschema/dtc warnings/errors:
Documentation/devicetree/bindings/i2c/i2c-mux-reg.example.dtb: /example-0/i2c-mux@6028/i2c@0/clock-generator@70: failed to match any schema with compatible: ['silabs,si5338']
Documentation/devicetree/bindings/i2c/i2c-mux-reg.example.dtb: /example-0/i2c-mux@6028/i2c@1/clock-generator@70: failed to match any schema with compatible: ['silabs,si5338']
doc reference errors (make refcheckdocs):
See https://patchwork.kernel.org/project/devicetree/patch/20260607-i2c-mux-reg-base-bus-num-v1-1-f193b5a8fedc@nexthop.ai
The base for the series is generally the latest rc1. A different dependency
should be noted in *this* patch.
If you already ran 'make dt_binding_check' and didn't see the above
error(s), then make sure 'yamllint' is installed and dt-schema is up to
date:
pip3 install dtschema --upgrade
Please check and re-submit after running the above command yourself. Note
that DT_SCHEMA_FILES can be set to your schema file to speed up checking
your schema. However, it must be unset to test all examples with your schema.
next prev parent reply other threads:[~2026-06-07 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-07 8:20 [PATCH 0/2] i2c: mux: reg: allow fixing the base bus number via fwnode Abdurrahman Hussain
2026-06-07 8:20 ` [PATCH 1/2] dt-bindings: i2c: convert i2c-mux-reg to DT schema Abdurrahman Hussain
2026-06-07 14:06 ` Conor Dooley
2026-06-08 0:39 ` Abdurrahman Hussain
2026-06-07 16:32 ` Rob Herring (Arm) [this message]
2026-06-07 8:20 ` [PATCH 2/2] i2c: mux: reg: allow fixing the base bus number via fwnode Abdurrahman Hussain
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=178084995520.4043722.11073475733919673696.robh@kernel.org \
--to=robh@kernel.org \
--cc=abdurrahman@nexthop.ai \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@lysator.liu.se \
/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