Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: 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>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] arm64: dts: zena: Add support for Zena CSS
Date: Thu, 5 Feb 2026 20:12:56 +0000	[thread overview]
Message-ID: <20260205-vagabond-silky-ape-dc9b8e@sudeepholla> (raw)
In-Reply-To: <76da2e9b-1b57-4bd1-b577-9001d01c7b9a@kernel.org>

On Thu, Feb 05, 2026 at 01:35:46PM +0100, Krzysztof Kozlowski wrote:
> On 23/01/2026 18:37, Debbie Horsfall wrote:
> > 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 <debbie.horsfall@arm.com>
> > ---
> >  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


      reply	other threads:[~2026-02-05 20:13 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
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 [this message]

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=20260205-vagabond-silky-ape-dc9b8e@sudeepholla \
    --to=sudeep.holla@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=debbie.horsfall@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@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 \
    /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