On Thu, Feb 05, 2026 at 01:35:46PM +0100, Krzysztof Kozlowski wrote:

On 23/01/2026 18:37, Debbie Horsfall wrote:

quoted

Introduce the Zena CSS Fixed Virtual Platform (FVP) dts. This is
currently the only Zena CSS variant, however the common definitions are
included in a common dtsi for extensibility.

Signed-off-by: Debbie Horsfall <redacted>
---
 MAINTAINERS                              |   1 +
 arch/arm64/boot/dts/arm/Makefile         |   1 +
 arch/arm64/boot/dts/arm/zena-css-fvp.dts |  55 ++
 arch/arm64/boot/dts/arm/zena-css.dtsi    | 826 +++++++++++++++++++++++++++++++
 4 files changed, 883 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 90d88137adf1..d1d2dae6a71e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS

@@ -3727,6 +3727,7 @@ ARM/ZENA CSS PLATFORM
 M:	Debbie Horsfall <debbie.horsfall@arm.com>
 S:	Maintained
 F:	Documentation/devicetree/bindings/arm/arm,zena-css.yaml
+F:	arch/arm64/boot/dts/arm/zena-css*

Eeeh, this is getting more and more messier.

All ARM designs or at least all similar like all ARM FVP should have one
group maintainers and that entry now claims "versatile express".

Sorry I saw that you have already pointed towards the above only after
I responded to 1/2. I agree this is not scalable and it is hard to categorise
them at the moment. Hopefully we may get more clarity in sometime in the
near future and we can rework them then. For now, your suggestion sounds
the best approach to take.

Additional entries for submaintainers is fine, but honestly with this
split of bindings this is getting more and more messier.

I know that ARM is kind of "special" but when it comes to SoCs it should
not be.

Sort out this mess, please, before get accept another platform.

Noted.

-- 
Regards,
Sudeep