mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Tomer Maimon <tmaimon77@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	 venture@google.com, yuenn@google.com, openbmc@lists.ozlabs.org,
	 benjaminfair@google.com, joel@jms.id.au, krzk+dt@kernel.org,
	 tali.perry1@gmail.com, conor+dt@kernel.org,
	avifishman70@gmail.com
Subject: Re: [PATCH v3 0/3] arm64: dts: nuvoton: add NPCM845 SoC and EVB support
Date: Fri, 26 Sep 2025 11:11:39 -0500	[thread overview]
Message-ID: <175890301752.880349.2331946518360447485.robh@kernel.org> (raw)
In-Reply-To: <20250925200625.573902-1-tmaimon77@gmail.com>


On Thu, 25 Sep 2025 23:06:22 +0300, Tomer Maimon wrote:
> This series fix warnings and adds device tree support for peripherals on
> the Nuvoton NPCM845 SoC and its Evaluation Board (EVB).
> The first patch fix warning and arrange node order.
> The second patch introduces peripheral nodes for Ethernet, MMC, SPI, USB,
> RNG, ADC, PWM-FAN, I2C, and OP-TEE firmware in the NPCM845 SoC device tree.
> The third patch enables these peripherals for the NPCM845-EVB, adding
> MDIO nodes, reserved memory, aliases, and board-specific configurations
> like PHY modes and SPI flash partitions.
> 
> The NPCM8XX device tree tested on NPCM845 evaluation board.
> 
> Addressed comments from:
> 	- Andrew Jeffery: https://patchwork.ozlabs.org/project/openbmc/patch/20250908125938.3584927-2-tmaimon77@gmail.com/
> 					  https://patchwork.ozlabs.org/project/openbmc/patch/20250908125938.3584927-3-tmaimon77@gmail.com/
> 
> Changes since version 2:
> 	- Fix dts warning
> 	- Arrange node order by ascending unit address.
> 
> Changes since version 1:
> 	- Fix commit message
> 	- Fix dtbs_check warnings.
> 
> Tomer Maimon (3):
>   arm64: dts: nuvoton: fix warning and nodes order
>   arm64: dts: nuvoton: npcm845: Add peripheral nodes
>   arm64: dts: nuvoton: npcm845-evb: Add peripheral nodes
> 
>  .../dts/nuvoton/nuvoton-common-npcm8xx.dtsi   | 732 +++++++++++++++++-
>  .../boot/dts/nuvoton/nuvoton-npcm845-evb.dts  | 440 +++++++++++
>  .../boot/dts/nuvoton/nuvoton-npcm845.dtsi     |   7 +
>  3 files changed, 1160 insertions(+), 19 deletions(-)
> 
> --
> 2.34.1
> 
> 
> 


My bot found new DTB warnings on the .dts files added or changed in this
series.

Some warnings may be from an existing SoC .dtsi. Or perhaps the warnings
are fixed by another series. Ultimately, it is up to the platform
maintainer whether these warnings are acceptable or not. No need to reply
unless the platform maintainer has comments.

If you already ran DT checks and didn't see these error(s), then
make sure dt-schema is up to date:

  pip3 install dtschema --upgrade


This patch series was applied (using b4) to base:
 Base: attempting to guess base-commit...
 Base: remotes/arm-soc/for-next-12027-gf60eaa447dab (exact match)

If this is not the correct base, please add 'base-commit' tag
(or use b4 which does this automatically)

New warnings running 'make CHECK_DTBS=y for arch/arm64/boot/dts/nuvoton/' for 20250925200625.573902-1-tmaimon77@gmail.com:

arch/arm64/boot/dts/nuvoton/nuvoton-npcm845-evb.dtb: /ahb/spi@fb000000: failed to match any schema with compatible: ['nuvoton,npcm845-fiu']
arch/arm64/boot/dts/nuvoton/nuvoton-npcm845-evb.dtb: /ahb/spi@fb002000: failed to match any schema with compatible: ['nuvoton,npcm845-fiu']
arch/arm64/boot/dts/nuvoton/nuvoton-npcm845-evb.dtb: /ahb/spi@c0000000: failed to match any schema with compatible: ['nuvoton,npcm845-fiu']
arch/arm64/boot/dts/nuvoton/nuvoton-npcm845-evb.dtb: /ahb/spi@fb001000: failed to match any schema with compatible: ['nuvoton,npcm845-fiu']
arch/arm64/boot/dts/nuvoton/nuvoton-npcm845-evb.dtb: /ahb/bus@f0000000/i2c@86000/tmp100@48: failed to match any schema with compatible: ['tmp100']
arch/arm64/boot/dts/nuvoton/nuvoton-npcm845-evb.dtb: /ahb/bus@f0000000/pwm-fan-controller@103000: failed to match any schema with compatible: ['nuvoton,npcm845-pwm-fan']
arch/arm64/boot/dts/nuvoton/nuvoton-npcm845-evb.dtb: /ahb/bus@f0000000/spi@201000: failed to match any schema with compatible: ['nuvoton,npcm845-pspi']






  parent reply	other threads:[~2025-09-26 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-25 20:06 Tomer Maimon
2025-09-25 20:06 ` [PATCH v3 1/3] arm64: dts: nuvoton: fix warning and nodes order Tomer Maimon
2025-10-19 10:35   ` Krzysztof Kozlowski
     [not found]     ` <CAP6Zq1i7repVa1oAVpyZxWw12-dv0MrVbkfXoqCKga+rp7=8LQ@mail.gmail.com>
2025-10-19 16:52       ` Krzysztof Kozlowski
2025-09-25 20:06 ` [PATCH v3 2/3] arm64: dts: nuvoton: npcm845: Add peripheral nodes Tomer Maimon
2025-09-25 20:06 ` [PATCH v3 3/3] arm64: dts: nuvoton: npcm845-evb: " Tomer Maimon
2025-09-26 16:11 ` Rob Herring (Arm) [this message]
2025-09-29  9:15   ` [PATCH v3 0/3] arm64: dts: nuvoton: add NPCM845 SoC and EVB support Tomer Maimon
2025-10-01  2:35     ` Andrew Jeffery
2025-10-16  9:06       ` Tomer Maimon

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=175890301752.880349.2331946518360447485.robh@kernel.org \
    --to=robh@kernel.org \
    --cc=avifishman70@gmail.com \
    --cc=benjaminfair@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.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

all inboxes | Powered by JetHome®