From: Conor Dooley <conor@kernel.org>
To: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
Cc: Jens Wiklander <jenswi@kernel.org>,
Sumit Garg <sumit.garg@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Rahul Pathak <rahul@summations.net>,
Anup Patel <anup@brainfault.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
op-tee@lists.trustedfirmware.org,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH RFC 5/5] dt-bindings: tee: add RISC-V RPMI TEE transport
Date: Tue, 15 Sep 2026 18:13:09 +0100 [thread overview]
Message-ID: <20260915-reappear-hatchback-f4c3697a1b4e@spud> (raw)
In-Reply-To: <20260912-rpmi-tee-service-grp-dev-v1-5-1d1d35c2a859@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 4032 bytes --]
On Sat, Sep 12, 2026 at 03:15:16AM -0700, Amirreza Zarrabi wrote:
> Add a device-tree binding for the OP-TEE RISC-V transport using the RPMI
> TEE service group over SBI MPXY.
>
> Describe one mailbox channel per hart and an optional interrupt used as
> the availability doorbell for asynchronous notifications.
>
> Add the binding to the existing OP-TEE MAINTAINERS entry.
>
> Signed-off-by: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
The clock and (?reset?) bindings for mpxy stuff have both S and M mode
bindings. How come you only have the S mode one here?
Cheers,
Conor.
> ---
> .../bindings/tee/riscv,rpmi-mpxy-tee.yaml | 65 ++++++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 66 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/tee/riscv,rpmi-mpxy-tee.yaml b/Documentation/devicetree/bindings/tee/riscv,rpmi-mpxy-tee.yaml
> new file mode 100644
> index 000000000000..8f6ff313fd42
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/tee/riscv,rpmi-mpxy-tee.yaml
> @@ -0,0 +1,65 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +# Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/tee/riscv,rpmi-mpxy-tee.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: RISC-V RPMI TEE service group based message proxy
> +
> +maintainers:
> + - Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
> +
> +description: |
> + The RISC-V Platform Management Interface (RPMI) [1] defines a messaging
> + protocol which is modular and extensible. The supervisor software can
> + send/receive RPMI messages via the SBI MPXY extension [2] or some dedicated
> + supervisor-mode RPMI transport.
> +
> + The RPMI specification [1] defines a TEE service group which is the RISC-V
> + analog of Arm FF-A: OP-TEE and the rich execution environment (REE, i.e.
> + Linux) are peer endpoints and the RPMI framework (machine mode firmware)
> + mediates every message. Entering OP-TEE on a hart runs it on that hart until
> + it responds, so the SBI implementation provides one SBI MPXY channel per
> + hart; all of them are listed, in hart order, on a single node.
> +
> + ===========================================
> + References
> + ===========================================
> +
> + [1] RISC-V Platform Management Interface (RPMI) v1.0 (or higher)
> + https://github.com/riscv-non-isa/riscv-rpmi/releases
> +
> + [2] RISC-V Supervisor Binary Interface (SBI) v3.0 (or higher)
> + https://github.com/riscv-non-isa/riscv-sbi-doc/releases
> +
> +properties:
> + compatible:
> + const: riscv,rpmi-mpxy-tee
> +
> + mboxes:
> + minItems: 1
> + description:
> + One SBI MPXY channel implementing the RPMI TEE service group per hart,
> + listed in the same order as the CPU nodes.
> +
> + interrupts:
> + maxItems: 1
> + description:
> + Availability doorbell raised by OP-TEE to signal asynchronous
> + notifications over the RPMI TEE signal bus. Optional; when absent
> + asynchronous notification is disabled.
> +
> +required:
> + - compatible
> + - mboxes
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + tee {
> + compatible = "riscv,rpmi-mpxy-tee";
> + mboxes = <&mpxy_mbox 0x10 0x0>, <&mpxy_mbox 0x11 0x0>;
> + };
> +...
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 207a6e2db70c..7d0e550085b2 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -20577,6 +20577,7 @@ M: Jens Wiklander <jenswi@kernel.org>
> L: op-tee@lists.trustedfirmware.org (moderated for non-subscribers)
> S: Maintained
> F: Documentation/ABI/testing/sysfs-bus-optee-devices
> +F: Documentation/devicetree/bindings/tee/riscv,rpmi-mpxy-tee.yaml
> F: drivers/tee/optee/
>
> OP-TEE RANDOM NUMBER GENERATOR (RNG) DRIVER
>
> --
> 2.34.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-09-15 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 10:15 [PATCH RFC 0/5] tee: optee: " Amirreza Zarrabi
2026-09-12 10:15 ` [PATCH RFC 1/5] optee: riscv: add RPMI TEE service group transport Amirreza Zarrabi
2026-09-16 5:30 ` Trilok Soni
2026-09-16 21:23 ` Amirreza Zarrabi
2026-09-12 10:15 ` [PATCH RFC 2/5] optee: riscv: add shared memory and scheduled calls Amirreza Zarrabi
2026-09-12 10:15 ` [PATCH RFC 3/5] optee: riscv: enable persistent shared argument cache Amirreza Zarrabi
2026-09-12 10:15 ` [PATCH RFC 4/5] optee: riscv: add asynchronous notifications over the signal bus Amirreza Zarrabi
2026-09-12 10:15 ` [PATCH RFC 5/5] dt-bindings: tee: add RISC-V RPMI TEE transport Amirreza Zarrabi
2026-09-15 17:13 ` Conor Dooley [this message]
2026-09-16 10:12 ` Anup Patel
2026-09-16 21:16 ` Amirreza Zarrabi
2026-09-17 8:38 ` Anup Patel
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=20260915-reappear-hatchback-f4c3697a1b4e@spud \
--to=conor@kernel.org \
--cc=alex@ghiti.fr \
--cc=amirreza.zarrabi@oss.qualcomm.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jenswi@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=rahul@summations.net \
--cc=robh@kernel.org \
--cc=sumit.garg@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
all inboxes | Powered by JetHome®