public inbox for linux-mips@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Jonas Gorski" <jonas.gorski@gmail.com>,
	"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: Re: [PATCH 4/4] mips: bmips: dts: fix qspi register order
Date: Thu, 25 Dec 2025 13:35:20 +0100	[thread overview]
Message-ID: <a31ece17-aac6-4369-b2ed-efd76e8961fe@kernel.org> (raw)
In-Reply-To: <20251225102533.30772-5-jonas.gorski@gmail.com>

On 25/12/2025 11:25, Jonas Gorski wrote:
> Align the register order to the schema. Fixes warnings like:
> 
> arch/mips/boot/dts/brcm/bcm97435svmb.dtb: spi@41d200 (brcm,spi-brcmstb-qspi): reg-names:0: 'cs_reg' is not one of ['hif_mspi', 'mspi']
> 	from schema $id: http://devicetree.org/schemas/spi/brcm,spi-bcm-qspi.yaml
> arch/mips/boot/dts/brcm/bcm97435svmb.dtb: spi@41d200 (brcm,spi-brcmstb-qspi): reg-names:1: 'bspi' was expected
> 	from schema $id: http://devicetree.org/schemas/spi/brcm,spi-bcm-qspi.yaml
> arch/mips/boot/dts/brcm/bcm97435svmb.dtb: spi@41d200 (brcm,spi-brcmstb-qspi): reg-names:2: 'bspi' is not one of ['intr_regs', 'intr_status_reg', 'cs_reg']
> 	from schema $id: http://devicetree.org/schemas/spi/brcm,spi-bcm-qspi.yaml

Trim redundant parts. You do not need to paste schema path every time.
Full path to DTB also is not really necessary, IMO.

> 
> Signed-off-by: Jonas Gorski <jonas.gorski@gmail.com>
> ---
>  arch/mips/boot/dts/brcm/bcm7125.dtsi | 4 ++--
>  arch/mips/boot/dts/brcm/bcm7346.dtsi | 4 ++--
>  arch/mips/boot/dts/brcm/bcm7358.dtsi | 4 ++--
>  arch/mips/boot/dts/brcm/bcm7360.dtsi | 4 ++--
>  arch/mips/boot/dts/brcm/bcm7362.dtsi | 4 ++--
>  arch/mips/boot/dts/brcm/bcm7420.dtsi | 4 ++--
>  arch/mips/boot/dts/brcm/bcm7425.dtsi | 4 ++--
>  arch/mips/boot/dts/brcm/bcm7435.dtsi | 4 ++--
>  8 files changed, 16 insertions(+), 16 deletions(-)
> 
> diff --git a/arch/mips/boot/dts/brcm/bcm7125.dtsi b/arch/mips/boot/dts/brcm/bcm7125.dtsi
> index dd1cc3cda694..81ee0f49b645 100644
> --- a/arch/mips/boot/dts/brcm/bcm7125.dtsi
> +++ b/arch/mips/boot/dts/brcm/bcm7125.dtsi
> @@ -250,8 +250,8 @@ qspi: spi@443000 {
>  			compatible = "brcm,spi-brcmstb-qspi",
>  				     "brcm,spi-bcm-qspi";
>  			clocks = <&upg_clk>;
> -			reg = <0x440920 0x4 0x443200 0x188 0x443000 0x50>;
> -			reg-names = "cs_reg", "hif_mspi", "bspi";
> +			reg = <0x443200 0x188 0x443000 0x50 0x440920 0x4>;
> +			reg-names = "hif_mspi", "bspi", "cs_reg";

So order is anyway broken by this change, thus you can as well rename it
to mspi, right?

Best regards,
Krzysztof

      reply	other threads:[~2025-12-25 12:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-25 10:25 [PATCH 0/4] mips: bmips: fix brcm,spi-bcm-qspi devicetree usage Jonas Gorski
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 [this message]

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=a31ece17-aac6-4369-b2ed-efd76e8961fe@kernel.org \
    --to=krzk@kernel.org \
    --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=jonas.gorski@gmail.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