From: Krzysztof Kozlowski <krzk@kernel.org>
To: Debbie Horsfall <debbie.horsfall@arm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liviu Dudau <liviu.dudau@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: Add Zena CSS compatibility
Date: Thu, 5 Feb 2026 13:29:18 +0100 [thread overview]
Message-ID: <762a8e34-e401-4b6c-ba73-35cfffcba4b2@kernel.org> (raw)
In-Reply-To: <20260123-zena-css-v1-1-34adb95cdf89@arm.com>
On 23/01/2026 18:37, Debbie Horsfall wrote:
> Add compatibility to Arm Zena CSS Fixed Virtual Platform [1].
>
> [1] https://www.arm.com/products/automotive/compute-subsystems/zena
>
> Signed-off-by: Debbie Horsfall <debbie.horsfall@arm.com>
> ---
> .../devicetree/bindings/arm/arm,zena-css.yaml | 31 ++++++++++++++++++++++
> MAINTAINERS | 5 ++++
> 2 files changed, 36 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/arm,zena-css.yaml b/Documentation/devicetree/bindings/arm/arm,zena-css.yaml
> new file mode 100644
> index 000000000000..42699b4db41e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/arm,zena-css.yaml
This should really go to one YAML file for most of FVP from ARM.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-05 12:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 17:37 [PATCH 0/2] Add Arm Zena CSS support Debbie Horsfall
2026-01-23 17:37 ` [PATCH 1/2] dt-bindings: arm: Add Zena CSS compatibility Debbie Horsfall
2026-01-26 15:46 ` Rob Herring (Arm)
2026-02-05 12:29 ` Krzysztof Kozlowski [this message]
2026-02-05 14:26 ` Sudeep Holla
2026-01-23 17:37 ` [PATCH 2/2] arm64: dts: zena: Add support for Zena CSS Debbie Horsfall
2026-01-27 13:22 ` Andre Przywara
2026-01-30 9:58 ` Debbie Horsfall
2026-01-30 10:31 ` Andre Przywara
2026-01-30 12:34 ` Sudeep Holla
2026-02-03 12:11 ` Cristian Marussi
2026-02-05 10:47 ` Debbie Horsfall
2026-02-05 11:08 ` Sudeep Holla
2026-02-05 11:24 ` Andre Przywara
2026-02-05 12:21 ` Sudeep Holla
2026-02-05 12:35 ` Krzysztof Kozlowski
2026-02-05 20:12 ` Sudeep Holla
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=762a8e34-e401-4b6c-ba73-35cfffcba4b2@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=debbie.horsfall@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.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