From: Yao Zi <me@ziyao.cc>
To: "Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Huacai Chen" <chenhuacai@kernel.org>,
"WANG Xuerui" <kernel@xen0n.name>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Binbin Zhou" <zhoubinbin@loongson.cn>
Cc: linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
Yao Zi <me@ziyao.cc>
Subject: [PATCH 0/2] Fix LoongArch dtbs_check warnings
Date: Tue, 9 Dec 2025 14:00:04 +0000 [thread overview]
Message-ID: <20251209140006.54821-1-me@ziyao.cc> (raw)
Running dtbs_check with ARCH=loongarch emits a lot of warnings, most
about describing sideband interrupts for PCI devices through interrupts
property, and usage of undocumented msi-parent property in pcie
controller in loongson-2k2000.dtsi.
Patch 1 solves the former problem by using interrupts-extended property
for these devices. I don't have LS2K1000/2000 devices on hand, so
helping in testing it will be appreciated. msi-parent property is
documented in the second patch for Loongson PCI controllers.
After applying the series, the only two warnings left are about naming
of I2C controllers,
/builder/repo/linux/arch/loongarch/boot/dts/loongson-2k1000-ref.dtb: i2c-gpio-0 (i2c-gpio): $nodename:0: 'i2c-gpio-0' does not match '^i2c(@.+|-[a-z0-9]+)?$'
from schema $id: http://devicetree.org/schemas/i2c/i2c-gpio.yaml#
/builder/repo/linux/arch/loongarch/boot/dts/loongson-2k1000-ref.dtb: i2c-gpio-1 (i2c-gpio): $nodename:0: 'i2c-gpio-1' does not match '^i2c(@.+|-[a-z0-9]+)?$'
from schema $id: http://devicetree.org/schemas/i2c/i2c-gpio.yaml#
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.
Thanks for your time and review.
Yao Zi (2):
LoongArch: dts: Describe PCI sideband IRQ through interrupt-extended
dt-bindings: PCI: loongson: Document msi-parent property
.../devicetree/bindings/pci/loongson.yaml | 2 ++
arch/loongarch/boot/dts/loongson-2k1000.dtsi | 25 ++++++---------
arch/loongarch/boot/dts/loongson-2k2000.dtsi | 32 +++++++------------
3 files changed, 23 insertions(+), 36 deletions(-)
--
2.51.2
next reply other threads:[~2025-12-09 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 14:00 Yao Zi [this message]
2025-12-09 14:00 ` [PATCH 1/2] LoongArch: dts: Describe PCI sideband IRQ through interrupt-extended Yao Zi
2025-12-09 14:00 ` [PATCH 2/2] dt-bindings: PCI: loongson: Document msi-parent property Yao Zi
2025-12-09 22:39 ` Rob Herring (Arm)
2025-12-10 5:22 ` Krzysztof Kozlowski
2026-01-13 13:32 ` (subset) [PATCH 0/2] Fix LoongArch dtbs_check warnings Manivannan Sadhasivam
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=20251209140006.54821-1-me@ziyao.cc \
--to=me@ziyao.cc \
--cc=bhelgaas@google.com \
--cc=chenhuacai@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel@xen0n.name \
--cc=krzk+dt@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--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
all inboxes | Powered by JetHome®