From: Jonas Gorski <jonas.gorski@gmail.com>
To: "Kamal Dasu" <kamal.dasu@broadcom.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>,
"Mark Brown" <broonie@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Rafał Miłecki" <rafal@milecki.pl>
Cc: Kamal Dasu <kdasu.kdev@gmail.com>,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org
Subject: [PATCH 0/4] mips: bmips: fix brcm,spi-bcm-qspi devicetree usage
Date: Thu, 25 Dec 2025 11:25:29 +0100 [thread overview]
Message-ID: <20251225102533.30772-1-jonas.gorski@gmail.com> (raw)
Currently running dtbs_check for BMIPS produces a lot of warnings. Start
addressing those by cleaning up the {q,m}spi nodes:
* allow the in-use hif_mspi as alternative register name
* fix compatible order from most to least specific
* reorder interrupt names matching the binding
* reorder register names matching the binding
This fixes all warnings issues by dtbs_check for the {q,m}spi nodes
themselves, and reduces the total amount of warnings generated from 416
to 368. I plan to address more in subsequent submissions.
No functional changes intended (I can't test them, since I don't have
any BCM7XXX boards at hand).
Jonas Gorski (4):
dt-bindings: brcm,spi-bcm-qspi: allow hif_mspi as alternative for mspi
mips: bmips: dts: fix {m,q}spi compatible order
mips: bmips: dts: fix qspi interrupt order
mips: bmips: dts: fix qspi register order
.../bindings/spi/brcm,spi-bcm-qspi.yaml | 2 +-
arch/mips/boot/dts/brcm/bcm7125.dtsi | 22 +++++++++----------
arch/mips/boot/dts/brcm/bcm7346.dtsi | 22 +++++++++----------
arch/mips/boot/dts/brcm/bcm7358.dtsi | 22 +++++++++----------
arch/mips/boot/dts/brcm/bcm7360.dtsi | 22 +++++++++----------
arch/mips/boot/dts/brcm/bcm7362.dtsi | 22 +++++++++----------
arch/mips/boot/dts/brcm/bcm7420.dtsi | 22 +++++++++----------
arch/mips/boot/dts/brcm/bcm7425.dtsi | 22 +++++++++----------
arch/mips/boot/dts/brcm/bcm7435.dtsi | 22 +++++++++----------
9 files changed, 89 insertions(+), 89 deletions(-)
--
2.43.0
next reply other threads:[~2025-12-25 10:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 10:25 Jonas Gorski [this message]
2025-12-25 10:25 ` [PATCH 1/4] dt-bindings: brcm,spi-bcm-qspi: allow hif_mspi as alternative for mspi Jonas Gorski
2025-12-25 12:32 ` Krzysztof Kozlowski
2025-12-25 12:34 ` Krzysztof Kozlowski
2025-12-25 10:25 ` [PATCH 2/4] mips: bmips: dts: fix {m,q}spi compatible order Jonas Gorski
2025-12-25 10:25 ` [PATCH 3/4] mips: bmips: dts: fix qspi interrupt order Jonas Gorski
2025-12-25 10:25 ` [PATCH 4/4] mips: bmips: dts: fix qspi register order Jonas Gorski
2025-12-25 12:35 ` Krzysztof Kozlowski
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=20251225102533.30772-1-jonas.gorski@gmail.com \
--to=jonas.gorski@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=kamal.dasu@broadcom.com \
--cc=kdasu.kdev@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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