Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Tomer Maimon" <tmaimon77@gmail.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v8 4/4] arm64: dts: nuvoton: npcm845-evb: Add peripheral nodes
Date: Wed, 08 Jul 2026 17:13:27 +0000	[thread overview]
Message-ID: <20260708171328.164201F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260708165929.2233934-5-tmaimon77@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The device tree aliases for the SPI FIU controllers `fiu1` and `fiu3` are incorrectly swapped.
--

--- Patch [4]: [PATCH v8 4/4] arm64: dts: nuvoton: npcm845-evb: Add peripheral nodes ---
commit 58cedbdc9355efee860c7d605886caa4e600ea8c
Author: Tomer Maimon <tmaimon77@gmail.com>

arm64: dts: nuvoton: npcm845-evb: Add peripheral nodes

Enable peripheral support for the NPCM845 evaluation board by wiring up
the SoC controller nodes to the board design. Add board aliases, GPIO-backed
MDIO buses, flash partitions, and enable various peripheral interfaces.

> diff --git a/arch/arm64/boot/dts/nuvoton/nuvoton-npcm845-evb.dts b/arch/arm64/boot/dts/nuvoton/nuvoton-npcm845-evb.dts
> index 5edf5d13342da..7717c3a8f76d2 100644
> --- a/arch/arm64/boot/dts/nuvoton/nuvoton-npcm845-evb.dts
> +++ b/arch/arm64/boot/dts/nuvoton/nuvoton-npcm845-evb.dts
> @@ -10,6 +10,42 @@ / {
>  
>  	aliases {
>  		serial0 = &serial0;
> +		ethernet1 = &gmac1;
> +		ethernet2 = &gmac2;
> +		ethernet3 = &gmac3;
> +		mdio-gpio0 = &mdio0;
> +		mdio-gpio1 = &mdio1;
> +		fiu0 = &fiu0;
> +		fiu1 = &fiu3;
> +		fiu2 = &fiux;
> +		fiu3 = &fiu1;

[Severity: Medium]
Are the aliases for the SPI FIU controllers intentionally swapped here?

Mapping fiu1 to &fiu3 and fiu3 to &fiu1 assigns logical SPI bus spi1 to the
&fiu3 hardware controller and spi3 to the &fiu1 hardware controller.

This contradicts the partition labels defined further down in this patch for
these nodes, which expect spi1 to be fiu1 and spi3 to be fiu3:

&fiu1 {
        ...
        partition@0 {
                label = "spi1-system1";

&fiu3 {
        ...
        partition@0 {
                label = "spi3-system1";

Could this mismatch break userspace and boot scripts relying on the logical
device IDs to find system partitions?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260708165929.2233934-1-tmaimon77@gmail.com?part=4

      reply	other threads:[~2026-07-08 17:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 16:59 [PATCH v8 0/4] arm64: dts: nuvoton: add NPCM845 SoC and EVB support Tomer Maimon
2026-07-08 16:59 ` [PATCH v8 1/4] arm64: dts: nuvoton: npcm845: Drop redundant timer clock-names Tomer Maimon
2026-07-08 16:59 ` [PATCH v8 2/4] arm64: dts: nuvoton: npcm845: Reorder timer0 and PECI nodes Tomer Maimon
2026-07-08 16:59 ` [PATCH v8 3/4] arm64: dts: nuvoton: npcm845: Add peripheral nodes Tomer Maimon
2026-07-08 17:15   ` sashiko-bot
2026-07-08 16:59 ` [PATCH v8 4/4] arm64: dts: nuvoton: npcm845-evb: " Tomer Maimon
2026-07-08 17:13   ` sashiko-bot [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=20260708171328.164201F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=tmaimon77@gmail.com \
    /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