From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, avifishman70@gmail.com,
tali.perry1@gmail.com, joel@jms.id.au, venture@google.com,
yuenn@google.com, benjaminfair@google.com,
openbmc@lists.ozlabs.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] arm64: dts: nuvoton: npcm845: Add peripheral nodes
Date: Mon, 22 Sep 2025 13:21:59 +0930 [thread overview]
Message-ID: <9ed40c5439dc8ecaa7b265e21d3cf15d45415bee.camel@codeconstruct.com.au> (raw)
In-Reply-To: <CAP6Zq1j83gOX0vGX3tR09c3S4_DSX4uCcM8TqbFxeP5zXNn2ng@mail.gmail.com>
Hi Tomer,
On Sun, 2025-09-21 at 18:56 +0300, Tomer Maimon wrote:
> Hi Andrew,
>
> Thanks for your comments.
>
> On Wed, 10 Sept 2025 at 10:52, Andrew Jeffery
> <andrew@codeconstruct.com.au> wrote:
> >
> > Hi Tomer,
> >
> > On Mon, 2025-09-08 at 15:59 +0300, Tomer Maimon wrote:
> > > Enable peripheral support for the Nuvoton NPCM845 SoC by adding
> > > device
> > > nodes for Ethernet controllers, MMC controller, SPI controllers,
> > > USB
> > > device controllers, random number generator, ADC, PWM-FAN
> > > controller,
> > > and I2C controllers. Include pinmux configurations for relevant
> > > peripherals to support hardware operation. Add an OP-TEE firmware
> > > node
> > > for secure services.
> > >
> > > Signed-off-by: Tomer Maimon <tmaimon77@gmail.com>
> > > ---
> > > .../dts/nuvoton/nuvoton-common-npcm8xx.dtsi | 702
> > > +++++++++++++++++-
> > > .../boot/dts/nuvoton/nuvoton-npcm845.dtsi | 7 +
> > > 2 files changed, 708 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/arch/arm64/boot/dts/nuvoton/nuvoton-common-
> > > npcm8xx.dtsi b/arch/arm64/boot/dts/nuvoton/nuvoton-common-
> > > npcm8xx.dtsi
> > > index 24133528b8e9..7f120da3310a 100644
> > >
> >
> > *snip*
> >
> > > + fiu1: spi@fb002000 {
> > > + compatible = "nuvoton,npcm845-fiu";
> > > + #address-cells = <1>;
> > > + #size-cells = <0>;
> > > + reg = <0x0 0xfb002000 0x0 0x1000>;
> > > + reg-names = "control";
> > > + clocks = <&clk NPCM8XX_CLK_SPI1>;
> > > + clock-names = "clk_spi1";
> > > + pinctrl-names = "default";
> > > + pinctrl-0 = <&spi1_pins>;
> > > + status = "disabled";
> > > + };
> > > +
> > > + fiu3: spi@c0000000 {
> > > + compatible = "nuvoton,npcm845-fiu";
> > > + #address-cells = <1>;
> > > + #size-cells = <0>;
> > > + reg = <0x0 0xc0000000 0x0 0x1000>;
> > > + reg-names = "control";
> > > + clocks = <&clk NPCM8XX_CLK_SPI3>;
> > > + clock-names = "clk_spi3";
> > > + pinctrl-names = "default";
> > > + pinctrl-0 = <&spi3_pins>;
> > > + status = "disabled";
> > > + };
> I don't need to move the FIU3 node as ordered by ascending unit
> address since the FIU3 node is a part of the FIU's group, am I
> correct?
It's acceptable by the linked coding standard, but my preference is for
the consistency of ordering by unit address.
> > > +
> > > + fiux: spi@fb001000 {
> > > + compatible = "nuvoton,npcm845-fiu";
> > > + #address-cells = <1>;
> > > + #size-cells = <0>;
> > > + reg = <0x0 0xfb001000 0x0 0x1000>,
> > > + <0x0 0xf8000000 0x0 0x2000000>;
> > > + reg-names = "control", "memory";
> > > + clocks = <&clk NPCM8XX_CLK_SPIX>;
> > > + clock-names = "clk_ahb";
> > > + status = "disabled";
> > > + };
> >
> > Can you please audit the patch (and the rest of the dtsi) to make
> > sure
> > all nodes are ordered by ascending unit address, as per the DTS
> > style
> > guide?
> >
> > https://docs.kernel.org/devicetree/bindings/dts-coding-style.html#order-of-nodes
> >
> > Andrew
> >
> > > +
> > > + mc: memory-controller@f0824000 {
> > > + compatible = "nuvoton,npcm845-memory-
> > > controller";
> > > + reg = <0x0 0xf0824000 0x0 0x1000>;
> > > + interrupts = <GIC_SPI 25
> > > IRQ_TYPE_LEVEL_HIGH>;
> > > + };
> > > +
> >
> > *snip*
>
> I see disorder in the upstream dtsi file, for example, PECI order. Do
> you suggest fixing it?
If you don't mind, yes please (... as a separate patch) :)
Andrew
next prev parent reply other threads:[~2025-09-22 3:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 12:59 [PATCH v2 0/2] arm64: dts: nuvoton: Add NPCM845 SoC and EVB support Tomer Maimon
2025-09-08 12:59 ` [PATCH v2 1/2] arm64: dts: nuvoton: npcm845: Add peripheral nodes Tomer Maimon
2025-09-10 7:52 ` Andrew Jeffery
2025-09-21 15:56 ` Tomer Maimon
2025-09-22 3:51 ` Andrew Jeffery [this message]
2025-09-08 12:59 ` [PATCH v2 2/2] arm64: dts: nuvoton: npcm845-evb: " Tomer Maimon
2025-09-10 7:56 ` Andrew Jeffery
2025-09-10 8:04 ` [PATCH v2 0/2] arm64: dts: nuvoton: Add NPCM845 SoC and EVB support Andrew Jeffery
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=9ed40c5439dc8ecaa7b265e21d3cf15d45415bee.camel@codeconstruct.com.au \
--to=andrew@codeconstruct.com.au \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
--cc=yuenn@google.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;
as well as URLs for NNTP newsgroup(s).