Re: [RFC PATCH] firmware: scmi: Make SCMI arch independent
From: Michal Simek
Date: Fri Jul 10 2026 - 03:06:39 EST
On 7/9/26 17:56, Cristian Marussi wrote:
On Thu, Jul 09, 2026 at 03:27:00PM +0200, Michal Simek wrote:
On heterogenious systems like AMD/Xilinx FPGA there is a need to talk to
SCMI server from different architectures than ARM that's why remove
ARM/ARM64 Kconfig dependency with also remove ARM from description and
rename folder to reflect it.
While I understand dropping the dependency on ARM (I always wanted to do
that and test if it worked at all on some otehr archs with QEMU), I am
not sure about the whole renaming party ? why is needed just for
cosmetic reasons ? it is at the end an arm originated protocol so I dont
see it as a being wrong to be named as such even though used by other
archs...I have not really strong opinion on this...
I have been in CC on U-Boot RPMI patches which got to my attention because
I don't want to have another interface for MB-V(riscv-) running in programmable logic and have another server in the system doing the same thing.
Based on that we had discussed about it with Vincent and Souvik (we missed you there) about using SCMI on non ARM platform and both of them didn't see the concern to be marked as ARM only protocol.
Truth is that some of protocols have ARM in description, file names, etc but some of them not. That's why I think it is good time to sync it up and enable
running this protocol on other SOCs.
... my concern really is ... wont this full scale rename simply generateI don't think it is going to be a big problem because it is just git mv which git is able to gracefully handle.
a lot of un-needed churn for future fixes and/or backporting ?
Thanks,
Michal