On 7/9/26 15:02, Michal Simek wrote:
On 7/8/26 23:51, Charles Perry wrote:
Hello,
This series adds support for RISC-V Platform Management Interface
(RPMI) to
U-Boot. RPMI is an OS-agnostic protocol for communication between an
Application Processor (AP) and a Platform Microcontroller (PuC) [1]. The
goals and purpose of RPMI are similar to ARM's SCMI.
From the first look it looks like SCMI. Why do you introducing
something what can be replaced by SCMI?
And SCMI has only specific ARM transport layer but the rest is arch
independent.
In our case where we have Microblaze V in programmable logic I can't see
any reason to use RPMI for talking to the same server if I need to do it
from ARM side too via SCMI.
I pretty much think that there should be communication with ARM and
instead of creating another firmware interface talk to each other and
have only one which can be used across multiple architectures.
Thanks,
Michal
Hello Michal,
The specifications for RISC-V are produced by RISC-V International. AMD
is a strategic member. Please, join the relevant technical groups to
collaborate on specifications.
RISC-V has defined the Supervisor Binary Interface (SBI) specification
which is available at
https://github.com/riscv-non-isa/riscv-sbi-doc/releases/download/v3.0/riscv-sbi.pdf.
The Message Proxy (MPXY) extension defines how communication channels
between different parts of software can be established.
RPMI is one of the defined messaging protocols. The ratified
specification is available at
https://github.com/riscv-non-isa/riscv-rpmi/releases/download/v1.0/riscv-rpmi.pdf.
Best regards
Heinrich
