linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Jeffery <andrew@codeconstruct.com.au>
To: Ryan Chen <ryan_chen@aspeedtech.com>
Cc: "Rob Herring (Arm)" <robh@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	soc@lists.linux.dev, Mo Elbadry <elbadrym@google.com>,
	 Arnd Bergmann <arnd@arndb.de>,
	William Kennington <wak@google.com>,
	Taniya Das <quic_tdas@quicinc.com>,
	linux-kernel@vger.kernel.org, spuranik@nvidia.com,
	 Eric Biggers <ebiggers@google.com>,
	Joel Stanley <joel@jms.id.au>,
	linux-aspeed@lists.ozlabs.org, Will Deacon <will@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Nishanth Menon <nm@ti.com>,
	Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	nfraprado@collabora.com,  linux-arm-kernel@lists.infradead.org,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Rom Lemarchand <romlem@google.com>,
	 devicetree@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	 leohu@nvidia.com,
	Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
	Yuxiao Zhang <yuxiaozhang@google.com>,
	dkodihalli@nvidia.com, wthai@nvidia.com
Subject: Re: [PATCH v0 0/5] Add initial AST2700 SoC support
Date: Fri, 13 Jun 2025 14:59:43 +0930	[thread overview]
Message-ID: <7b3be5c104b1fe1033570f2f3e2391991b6d9d42.camel@codeconstruct.com.au> (raw)
In-Reply-To: <174975871838.2916138.1953670783794758715.robh@kernel.org>

On Thu, 2025-06-12 at 15:12 -0500, Rob Herring (Arm) wrote:
> 
> On Thu, 12 Jun 2025 18:09:28 +0800, Ryan Chen wrote:
> > This patch series introduces initial support for the Aspeed AST2700 SoC
> > and the AST2700 Evaluation Board (EVB) to the Linux kernel. The AST2700
> > is the 7th generation Baseboard Management Controller (BMC) SoC from Aspeed,
> > featuring improved performance, enhanced security, and expanded I/O
> > capabilities compared to previous generations.
> > 
> > The patchset includes the following changes:
> > - Device tree bindings for AST2700 boards.
> > - Addition of the AST2700 platform to the Kconfig menu.
> > - Basic device tree for the AST2700 SoC.
> > - Device tree for the AST2700-EVB.
> > - Updated defconfig to enable essential options for AST2700.
> > 
> > Ryan Chen (5):
> >   dt-bindings: arm: aspeed: Add AST2700 board compatible
> >   arm64: Kconfig: Add Aspeed SoC family (ast2700) platform option
> >   arm64: dts: aspeed: Add initial AST2700 SoC device tree
> >   arm64: dts: aspeed: Add AST2700 EVB device tree
> >   arm64: configs: Update defconfig for AST2700 platform support
> > 
> >  .../bindings/arm/aspeed/aspeed.yaml           |   5 +
> >  arch/arm64/Kconfig.platforms                  |   6 +
> >  arch/arm64/boot/dts/Makefile                  |   1 +
> >  arch/arm64/boot/dts/aspeed/Makefile           |   4 +
> >  arch/arm64/boot/dts/aspeed/aspeed-g7.dtsi     | 380 ++++++++++++++++++
> >  arch/arm64/boot/dts/aspeed/ast2700-evb.dts    |  54 +++
> >  arch/arm64/configs/defconfig                  |   1 +
> >  7 files changed, 451 insertions(+)
> >  create mode 100644 arch/arm64/boot/dts/aspeed/Makefile
> >  create mode 100644 arch/arm64/boot/dts/aspeed/aspeed-g7.dtsi
> >  create mode 100644 arch/arm64/boot/dts/aspeed/ast2700-evb.dts
> > 
> > --
> > 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: tags/v6.16-rc1 (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/aspeed/' for 20250612100933.3007673-1-ryan_chen@aspeedtech.com:
> 
> arch/arm64/boot/dts/aspeed/ast2700-evb.dtb: serial@14c33b00 (ns16550a): 'pinctrl-0' is a dependency of 'pinctrl-names'
>         from schema $id: http://devicetree.org/schemas/pinctrl/pinctrl-consumer.yaml#
> arch/arm64/boot/dts/aspeed/ast2700-evb.dtb: interrupt-controller@100 (aspeed,ast2700-intc-ic): interrupts-extended: [[6, 0, 3844]] is too short
>         from schema $id: http://devicetree.org/schemas/interrupt-controller/aspeed,ast2700-intc.yaml#
> arch/arm64/boot/dts/aspeed/ast2700-evb.dtb: interrupt-controller@110 (aspeed,ast2700-intc-ic): interrupts-extended: [[6, 1, 3844]] is too short
>         from schema $id: http://devicetree.org/schemas/interrupt-controller/aspeed,ast2700-intc.yaml#
> arch/arm64/boot/dts/aspeed/ast2700-evb.dtb: interrupt-controller@120 (aspeed,ast2700-intc-ic): interrupts-extended: [[6, 2, 3844]] is too short
>         from schema $id: http://devicetree.org/schemas/interrupt-controller/aspeed,ast2700-intc.yaml#
> arch/arm64/boot/dts/aspeed/ast2700-evb.dtb: interrupt-controller@130 (aspeed,ast2700-intc-ic): interrupts-extended: [[6, 3, 3844]] is too short
>         from schema $id: http://devicetree.org/schemas/interrupt-controller/aspeed,ast2700-intc.yaml#
> arch/arm64/boot/dts/aspeed/ast2700-evb.dtb: interrupt-controller@140 (aspeed,ast2700-intc-ic): interrupts-extended: [[6, 4, 3844]] is too short
>         from schema $id: http://devicetree.org/schemas/interrupt-controller/aspeed,ast2700-intc.yaml#
> arch/arm64/boot/dts/aspeed/ast2700-evb.dtb: interrupt-controller@150 (aspeed,ast2700-intc-ic): interrupts-extended: [[6, 5, 3844]] is too short
>         from schema $id: http://devicetree.org/schemas/interrupt-controller/aspeed,ast2700-intc.yaml#
> 

To draw a line in the sand here: while the existing Aspeed devicetrees
(AST2600 and below) produce warnings, I won't accept devicetree patches
for the AST2700 and related boards unless they are warning-free.

Please make sure to test with the dt_binding_check and dtbs_check
targets (or equivalent) before sending your patches.

Andrew


  reply	other threads:[~2025-06-13  5:38 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12 10:09 [PATCH v0 0/5] Add initial AST2700 SoC support Ryan Chen
2025-06-12 10:09 ` [PATCH v0 1/5] dt-bindings: arm: aspeed: Add AST2700 board compatible Ryan Chen
2025-06-12 10:15   ` Krzysztof Kozlowski
2025-06-13  2:00     ` Ryan Chen
2025-06-12 10:09 ` [PATCH v0 2/5] arm64: Kconfig: Add Aspeed SoC family (ast2700) platform option Ryan Chen
2025-06-12 10:09 ` [PATCH v0 3/5] arm64: dts: aspeed: Add initial AST2700 SoC device tree Ryan Chen
2025-06-12 10:17   ` Krzysztof Kozlowski
2025-06-13  2:29     ` Ryan Chen
2025-06-13  6:16       ` Krzysztof Kozlowski
2025-06-16  2:24         ` Ryan Chen
2025-06-16  6:15           ` Krzysztof Kozlowski
2025-06-16  6:32             ` Ryan Chen
2025-06-16  6:43               ` Krzysztof Kozlowski
2025-06-16  6:54                 ` Ryan Chen
2025-06-16  7:07                   ` Krzysztof Kozlowski
2025-06-16  7:52                     ` Ryan Chen
2025-06-16 10:29                       ` Krzysztof Kozlowski
2025-06-12 10:20   ` Krzysztof Kozlowski
2025-06-13  2:54     ` Ryan Chen
2025-06-12 10:09 ` [PATCH v0 4/5] arm64: dts: aspeed: Add AST2700 EVB " Ryan Chen
2025-06-12 10:14   ` Krzysztof Kozlowski
2025-06-12 10:14     ` Krzysztof Kozlowski
2025-06-12 10:09 ` [PATCH v0 5/5] arm64: configs: Update defconfig for AST2700 platform support Ryan Chen
2025-06-12 10:18   ` Krzysztof Kozlowski
2025-06-12 20:12 ` [PATCH v0 0/5] Add initial AST2700 SoC support Rob Herring (Arm)
2025-06-13  5:29   ` Andrew Jeffery [this message]
2025-06-25 20:42     ` Rob Herring

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=7b3be5c104b1fe1033570f2f3e2391991b6d9d42.camel@codeconstruct.com.au \
    --to=andrew@codeconstruct.com.au \
    --cc=arnd@arndb.de \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dkodihalli@nvidia.com \
    --cc=ebiggers@google.com \
    --cc=elbadrym@google.com \
    --cc=geert@linux-m68k.org \
    --cc=joel@jms.id.au \
    --cc=krzk+dt@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=leohu@nvidia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfraprado@collabora.com \
    --cc=nm@ti.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=quic_tdas@quicinc.com \
    --cc=robh@kernel.org \
    --cc=romlem@google.com \
    --cc=ryan_chen@aspeedtech.com \
    --cc=soc@lists.linux.dev \
    --cc=spuranik@nvidia.com \
    --cc=wak@google.com \
    --cc=will@kernel.org \
    --cc=wthai@nvidia.com \
    --cc=yuxiaozhang@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).