From: Yao Zi <me@ziyao.cc>
To: Binbin Zhou <zhoubinbin@loongson.cn>,
Binbin Zhou <zhoubb.aaron@gmail.com>,
Huacai Chen <chenhuacai@loongson.cn>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Huacai Chen <chenhuacai@kernel.org>,
Xuerui Wang <kernel@xen0n.name>,
loongarch@lists.linux.dev, devicetree@vger.kernel.org
Subject: Re: [PATCH 7/7] LoongArch: dts: loongson-2k1000: Fix i2c-gpio node names
Date: Tue, 16 Dec 2025 09:44:26 +0000 [thread overview]
Message-ID: <aUEp-pEwHk0Ls6CD@pie> (raw)
In-Reply-To: <9684ae4e58fd1e9768cccf6e3ae730eff46fb29c.1765778124.git.zhoubinbin@loongson.cn>
On Tue, Dec 16, 2025 at 03:56:59PM +0800, Binbin Zhou wrote:
> From: Binbin Zhou <zhoubb.aaron@gmail.com>
>
> The binding wants the node to be named "i2c-number", alternatively
> "i2c@address", but those are named "i2c-gpio-number" instead.
>
> Rename those to i2c-0, i2c-1 to adhere to the binding and suppress
> dtbs_check warnings.
I think this is an unintended breakage in dtschema upstream, but not
really a violation. As I've mentioned in my original cover-letter,
> which IMHO is a regression caused by dt-schema commit 57138f5b8c92
> ("schemas: i2c: Avoid extra characters in i2c nodename pattern"). Commit
> 647181a1f8ff ("schemas: i2c: Allow for 'i2c-.*' node names") fails to
> fix the case, as it doesn't take nodenames with multiple hyphens in
> account. I'll start a separate series for this.
So I think it should probably be fixed in dt-schema instead. i2c-gpio-X
provides more information to me, and I don't think it causes any
inconsistency or ambiguity.
By the way, we also have dozens of arm dtb targets shipping nodes named
like i2c-gpio-*, mostly microchip and st ones, fixing the regex in
dtschema upstream will also eliminate warnings for them.
Best regards,
Yao Zi
> Signed-off-by: Binbin Zhou <zhoubb.aaron@gmail.com>
> ---
> arch/loongarch/boot/dts/loongson-2k1000.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/loongarch/boot/dts/loongson-2k1000.dtsi b/arch/loongarch/boot/dts/loongson-2k1000.dtsi
> index fa1c000fd3e0..f70b245c8bc4 100644
> --- a/arch/loongarch/boot/dts/loongson-2k1000.dtsi
> +++ b/arch/loongarch/boot/dts/loongson-2k1000.dtsi
> @@ -46,7 +46,7 @@ cpuintc: interrupt-controller {
> };
>
> /* i2c of the dvi eeprom edid */
> - i2c-gpio-0 {
> + i2c-0 {
> compatible = "i2c-gpio";
> scl-gpios = <&gpio0 0 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
> sda-gpios = <&gpio0 1 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
> @@ -57,7 +57,7 @@ i2c-gpio-0 {
> };
>
> /* i2c of the eeprom edid */
> - i2c-gpio-1 {
> + i2c-1 {
> compatible = "i2c-gpio";
> scl-gpios = <&gpio0 33 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
> sda-gpios = <&gpio0 32 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
> --
> 2.47.3
>
next prev parent reply other threads:[~2025-12-16 9:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 7:54 [PATCH 0/7] LoongArch: DTS: Fix dtbs_check warnings Binbin Zhou
2025-12-16 7:54 ` [PATCH 1/7] dt-bindings: PCI: loongson: Document msi-parent property Binbin Zhou
2025-12-16 7:55 ` [PATCH 2/7] dt-bindings: interrupt-controller: loongson,pch-pic: Change to unevaluatedProperties Binbin Zhou
2025-12-16 16:16 ` Rob Herring
2025-12-17 7:17 ` Binbin Zhou
2025-12-16 7:55 ` [PATCH 3/7] LoongArch: dts: Describe PCI sideband IRQ through interrupt-extended Binbin Zhou
2025-12-16 7:56 ` [PATCH 4/7] LoongArch: dts: loongson-2k0500: Add default Extend I/O Interrupt controller address cells Binbin Zhou
2025-12-16 7:56 ` [PATCH 5/7] LoongArch: dts: loongson-2k1000: Add default Local " Binbin Zhou
2025-12-17 4:49 ` Huacai Chen
2025-12-16 7:56 ` [PATCH 6/7] LoongArch: dts: loongson-2k2000: Add default PCH PIC " Binbin Zhou
2025-12-16 7:56 ` [PATCH 7/7] LoongArch: dts: loongson-2k1000: Fix i2c-gpio node names Binbin Zhou
2025-12-16 9:44 ` Yao Zi [this message]
2025-12-16 16:24 ` Krzysztof Kozlowski
2025-12-16 16:25 ` Krzysztof Kozlowski
2025-12-16 9:31 ` [PATCH 0/7] LoongArch: DTS: Fix dtbs_check warnings Yao Zi
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=aUEp-pEwHk0Ls6CD@pie \
--to=me@ziyao.cc \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@xen0n.name \
--cc=krzk+dt@kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=robh+dt@kernel.org \
--cc=zhoubb.aaron@gmail.com \
--cc=zhoubinbin@loongson.cn \
/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).