From: Conor Dooley <conor@kernel.org>
To: xianwei.zhao@amlogic.com
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] dt-bindings: arm: amlogic: meson-gx-ao-secure: support more SoCs
Date: Mon, 17 Nov 2025 19:25:22 +0000 [thread overview]
Message-ID: <20251117-cement-hasty-15626e8c78a0@spud> (raw)
In-Reply-To: <20251117-soc-info-s6-s7-s7d-v1-1-6ab8aab03dce@amlogic.com>
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
On Mon, Nov 17, 2025 at 06:17:00PM +0800, Xianwei Zhao via B4 Relay wrote:
> From: Xianwei Zhao <xianwei.zhao@amlogic.com>
>
> Add new compatible for ao-secure of Amlogic SoCs(S6,S7,S7D).
>
> Signed-off-by: Xianwei Zhao <xianwei.zhao@amlogic.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: not-applicable
> ---
> .../devicetree/bindings/arm/amlogic/amlogic,meson-gx-ao-secure.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/amlogic/amlogic,meson-gx-ao-secure.yaml b/Documentation/devicetree/bindings/arm/amlogic/amlogic,meson-gx-ao-secure.yaml
> index b4f6695a6015..fa7c403c874a 100644
> --- a/Documentation/devicetree/bindings/arm/amlogic/amlogic,meson-gx-ao-secure.yaml
> +++ b/Documentation/devicetree/bindings/arm/amlogic/amlogic,meson-gx-ao-secure.yaml
> @@ -34,6 +34,9 @@ properties:
> - amlogic,a4-ao-secure
> - amlogic,c3-ao-secure
> - amlogic,s4-ao-secure
> + - amlogic,s6-ao-secure
> + - amlogic,s7-ao-secure
> + - amlogic,s7d-ao-secure
> - amlogic,t7-ao-secure
> - const: amlogic,meson-gx-ao-secure
> - const: syscon
>
> --
> 2.37.1
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-11-17 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 10:16 [PATCH 0/5] soc: amlogic: Add new Amlogic SoCs info defines Xianwei Zhao via B4 Relay
2025-11-17 10:17 ` [PATCH 1/5] dt-bindings: arm: amlogic: meson-gx-ao-secure: support more SoCs Xianwei Zhao via B4 Relay
2025-11-17 19:25 ` Conor Dooley [this message]
2025-11-17 10:17 ` [PATCH 2/5] soc: amlogic: meson-gx-socinfo: add new SoCs id Xianwei Zhao via B4 Relay
2025-11-17 10:19 ` Neil Armstrong
2025-11-18 2:07 ` Xianwei Zhao
2025-11-17 10:17 ` [PATCH 3/5] arm64: dts: amlogic: s6: add ao secure node Xianwei Zhao via B4 Relay
2025-11-17 10:17 ` [PATCH 4/5] arm64: dts: amlogic: s7: " Xianwei Zhao via B4 Relay
2025-11-17 10:17 ` [PATCH 5/5] arm64: dts: amlogic: s7d: " Xianwei Zhao via B4 Relay
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=20251117-cement-hasty-15626e8c78a0@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=xianwei.zhao@amlogic.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