[PATCH RFC 01/18] firmware: arm_scmi: Allow SCMI transports on RISC-V

[Sudeep Holla]

On Tue, Oct 27, 2026 at 04:51:36PM +0100, Michal Simek wrote:
> 
> 
> On 10/27/26 16:36, Han Gao via B4 Relay wrote:
> > From: Han Gao <gaohan at iscas.ac.cn>
> > 
> > Mailbox and shared-memory SCMI transports do not require ARM execution.
> > Allow RISC-V platforms to use the existing SCMI core and protocol drivers;
> > architecture-specific transports retain their own dependencies.
> > 
> > Signed-off-by: Han Gao <gaohan at iscas.ac.cn>
> > ---
> >   drivers/firmware/arm_scmi/Kconfig | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/firmware/arm_scmi/Kconfig b/drivers/firmware/arm_scmi/Kconfig
> > index 783c24a20e29..1cfe2b572d18 100644
> > --- a/drivers/firmware/arm_scmi/Kconfig
> > +++ b/drivers/firmware/arm_scmi/Kconfig
> > @@ -3,7 +3,7 @@ menu "ARM System Control and Management Interface Protocol"
> >   config ARM_SCMI_PROTOCOL
> >   	tristate "ARM System Control and Management Interface (SCMI) Message Protocol"
> > -	depends on ARM || ARM64 || COMPILE_TEST
> > +	depends on ARM || ARM64 || RISCV || COMPILE_TEST
> 
> 
> I would prefer to remove ARM || ARM64 dependencies completely that you don't
> need to add RISCV there.
> 

Agreed. Before merging, we should trigger exploratory builds across multiple
architectures. This will help us catch any hardware-specific dependencies,
such as arch-exclusive IO accessors, that I might be overlooking right now.

-- 
Regards,
Sudeep