Re: [RFC PATCH] firmware: scmi: Make SCMI arch independent
Ulf Hansson <[email protected]> Tue, 14 Jul 2026 15:16:07 +0200
| Newsgroups | org.kernel.vger.arm-scmi,dev.linux.lists.imx,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-clk,org.kernel.vger.linux-doc,org.kernel.vger.linux-gpio,org.kernel.vger.linux-hwmon,org.kernel.vger.linux-iio,org.kernel.vger.linux-kernel,org.kernel.vger.linux-pm |
|---|---|
| Message-ID | <CAPx+jO9KMcxnmt-wT5jaApj9p7s11B6eSG6K08Jt9J=-vXxjhA@mail.gmail.com> |
On Thu, Jul 9, 2026 at 5:56 PM Cristian Marussi <[email protected]> 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... This is certainly not my call to make, but I have to admit that I fully agree with the above. Usually we don't rename files that indicate a legacy platform name, just because a new company/platform wants to make use of it. > > ... my concern really is ... wont this full scale rename simply generate > a lot of un-needed churn for future fixes and/or backporting ? We have some git magic to overcome most of these problems, but it's not always straightforward, I think. > > Thanks, > Cristian Kind regards Uffe