From: Sudeep Holla <sudeep.holla@kernel.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Debbie Horsfall <debbie.horsfall@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Rob Herring <robh@kernel.org>,
Sudeep Holla <sudeep.holla@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: Fri, 30 Jan 2026 12:34:31 +0000 [thread overview]
Message-ID: <20260130-light-piquant-termite-fcbec4@sudeepholla> (raw)
In-Reply-To: <8c343e6d-14f8-4f55-8218-bc3f0813e8cf@arm.com>
+Cristian(in case I am talking no sense)
On Fri, Jan 30, 2026 at 11:31:25AM +0100, Andre Przywara wrote:
>
> So do you need just one "tx", but "rx" plus "rx_reply"? Which isn't valid in
> the current binding?
> If that's the case, then we would need a patch to relax the binding and
> allowing this combination as well.
> Looking into the kernel code it looks like the SCMI driver doesn't use
> mbox-names, but explicitly expects assignments depending on the number of
> mboxes? Somewhat confusing ...
>
It is generally transmitted via tx, and tx_reply is necessary when the
platform has unidirectional channels. tx_reply is used to determine when the
synchronization commands have completed, without requiring polling of the
shared memory. rx_reply is necessary only if the platform firmware expects
it and doesn't poll the shared memory for OSPM/agent acknowledgement.
--
Regards,
Sudeep
next prev parent reply other threads:[~2026-01-30 12:34 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 [this message]
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=20260130-light-piquant-termite-fcbec4@sudeepholla \
--to=sudeep.holla@kernel.org \
--cc=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 \
/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