From: Conor Dooley <conor@kernel.org>
To: Ryan Chen <ryan_chen@aspeedtech.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@codeconstruct.com.au>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Nishanth Menon <nm@ti.com>,
nfraprado@collabora.com, Taniya Das <quic_tdas@quicinc.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Eric Biggers <ebiggers@google.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
soc@lists.linux.dev, Mo Elbadry <elbadrym@google.com>,
Rom Lemarchand <romlem@google.com>,
William Kennington <wak@google.com>,
Yuxiao Zhang <yuxiaozhang@google.com>,
wthai@nvidia.com, leohu@nvidia.com, dkodihalli@nvidia.com,
spuranik@nvidia.com
Subject: Re: [PATCH v4 1/5] dt-bindings: arm: aspeed: Add AST2700 board compatible
Date: Thu, 21 Aug 2025 19:09:01 +0100 [thread overview]
Message-ID: <20250821-nineteen-purveyor-a5fe7e86296c@spud> (raw)
In-Reply-To: <20250821080214.513090-2-ryan_chen@aspeedtech.com>
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
On Thu, Aug 21, 2025 at 04:02:10PM +0800, Ryan Chen wrote:
> Add device tree compatible string for AST2700 based boards
> ("aspeed,ast2700-evb" and "aspeed,ast2700") to the Aspeed SoC
> board bindings. This allows proper schema validation and
> enables support for AST2700 platforms.
>
> Signed-off-by: Ryan Chen <ryan_chen@aspeedtech.com>
> ---
> Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml b/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
> index 01333ac111fb..660529c81af9 100644
> --- a/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
> +++ b/Documentation/devicetree/bindings/arm/aspeed/aspeed.yaml
> @@ -102,5 +102,10 @@ properties:
> - quanta,s6q-bmc
> - ufispace,ncplite-bmc
> - const: aspeed,ast2600
Missing blank line here. Otherwisem
Acked-by: Conor Dooley <conor.dooley@microchip.com>
> + - description: AST2700 based boards
> + items:
> + - enum:
> + - aspeed,ast2700-evb
> + - const: aspeed,ast2700
>
> additionalProperties: true
> --
> 2.34.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-08-21 23:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 8:02 [PATCH v4 0/5] Introduce ASPEED AST2700 BMC SoC Ryan Chen
2025-08-21 8:02 ` [PATCH v4 1/5] dt-bindings: arm: aspeed: Add AST2700 board compatible Ryan Chen
2025-08-21 18:09 ` Conor Dooley [this message]
2025-08-21 8:02 ` [PATCH v4 2/5] arm64: Kconfig: Add Aspeed SoC family (ast27XX) Kconfig support Ryan Chen
2025-08-21 8:02 ` [PATCH v4 3/5] arm64: dts: aspeed: Add initial AST2700 SoC device tree Ryan Chen
2025-08-21 8:02 ` [PATCH v4 4/5] arm64: dts: aspeed: Add AST2700 Evaluation Board Ryan Chen
2025-08-21 8:02 ` [PATCH v4 5/5] arm64: configs: Update defconfig for AST2700 platform support Ryan Chen
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=20250821-nineteen-purveyor-a5fe7e86296c@spud \
--to=conor@kernel.org \
--cc=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