On 10/13/26 08:49, Michal Simek wrote:
On 10/13/26 01:55, Charles Perry wrote:
On Mon, Oct 12, 2026 at 11:47:51AM +0200, Michal Simek wrote:
Hi, +Paul
Hello Michal,
first of all do not use mailing list on denx.de.
Ok, I sent this series at around the time U-Boot changed to
[email protected]. Sorry for that.
On 9/2/26 16:17, 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.
I have raised my concern at riscv minisummit at LPC and also talked
to Paul
(riscv kernel maintainer) that this is not the right way to go. We
already
have SCMI and there is no reason to introduce RPMI when it is said it is
serving the same purpose.
Cool! Thanks for bringing this topic to LPC!
That being said, I don't understand why we can't have both SCMI and RPMI.
For sure its more code to maintain, but there are other things at play
than
just the functionnality. We discussed this in v2 [1], the points of
contention were:
* Anup said that the main blocker for him is that the SCMI spec is not
community driven while RPMI is.
Based on my information none really starts to talk to ARM about SCMI and
this has been introduced serving the same purpose. None should introduce
another interface which does the same thing. That never was the right
way to go.
Thanks,
Michal
Hello Michal,
RPMI is already used in the Linux kernel since 2025.
U-Boot has already lot of alternative interfaces implemented:
* Xen and QEMU/KVM
* half a dozen file systems
* MBR and GPT
* FIT images and UEFI
I can't see anything special about RPMI.
As nobody, including you, seems to be interested in driving a discussion
with ARM which would set back RISC-V for months or years, we should
proceed implementing what is needed.
Best regards
Heinrich
