From: Andre Przywara <andre.przywara@arm.com>
To: Sudeep Holla <sudeep.holla@kernel.org>,
Cristian Marussi <cristian.marussi@arm.com>
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 12:24:58 +0100 [thread overview]
Message-ID: <445035bb-71be-4751-a014-9ca67b1c0cb4@arm.com> (raw)
In-Reply-To: <20260205-intelligent-intrepid-robin-df42bd@sudeepholla>
On 2/5/26 12:08, Sudeep Holla wrote:
> On Tue, Feb 03, 2026 at 12:11:57PM +0000, Cristian Marussi wrote:
>>
>> All of this madness was the best way I could find to address the problem
>> of supporting such new unidirectional mailboxes in the SCMI while NOT
>> breaking backward compatibility in the absence of mandatory naming from
>> the start.
>>
>
> You can attribute this to my expecting an overly ideal scenario with
> bidirectional mailbox channels across all platforms using SCMI. At the time, I
> did not anticipate the range of configurations that rely on unidirectional
> channels.
Would it make sense then to add mbox-names parsing to the code, to
accommodate new users? There is precedence in some drivers for
introducing xyz-names for clearer and unambiguous resolution, while
still falling back to some legacy, fixed associations in case the names
property doesn't exist.
Cheers,
Andre
next prev parent reply other threads:[~2026-02-05 11:25 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 [this message]
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=445035bb-71be-4751-a014-9ca67b1c0cb4@arm.com \
--to=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=cristian.marussi@arm.com \
--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@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