From: Michal Simek <michal.simek@amd.com>
To: gaohan@iscas.ac.cn, Sudeep Holla <sudeep.holla@kernel.org>,
Cristian Marussi <cristian.marussi@arm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
Zhiguo Zhu <zhiguo.zhu@linux.alibaba.com>,
Jassi Brar <jassisinghbrar@gmail.com>,
Linus Walleij <linusw@kernel.org>,
Bartosz Golaszewski <brgl@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Thomas Gleixner <tglx@kernel.org>, Radu Rendec <radu@rendec.net>,
Samuel Holland <samuel.holland@sifive.com>,
Daniel Lezcano <daniel.lezcano@kernel.org>,
Anup Patel <anup@brainfault.org>, Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney+clk@redhat.com>,
Jerome Brunet <jbrunet+clk@baylibre.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Drew Fustini <fustini@kernel.org>, Icenowy Zheng <uwu@icenowy.me>,
Inochi Amaoto <inochiama@gmail.com>,
Vivian Wang <wangruikang@iscas.ac.cn>, Yao Zi <me@ziyao.cc>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-gpio@vger.kernel.org,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-clk@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH RFC 01/18] firmware: arm_scmi: Allow SCMI transports on RISC-V
Date: Tue, 27 Oct 2026 16:51:36 +0100 [thread overview]
Message-ID: <3d38c4a5-1a12-4af1-ac2e-413a457ce4c5@amd.com> (raw)
In-Reply-To: <20261027-a210-scmi-v1-1-74d58ce85bd8@iscas.ac.cn>
On 10/27/26 16:36, Han Gao via B4 Relay wrote:
> From: Han Gao <gaohan@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@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.
Thanks,
Michal
next prev parent reply other threads:[~2026-10-27 15:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 15:36 [PATCH RFC 00/18] riscv: add initial Zhihe A210 support using SCMI clocks and resets Han Gao via B4 Relay
2026-10-27 15:36 ` [PATCH RFC 01/18] firmware: arm_scmi: Allow SCMI transports on RISC-V Han Gao via B4 Relay
2026-10-27 15:51 ` Michal Simek [this message]
2026-10-27 16:18 ` Sudeep Holla
2026-10-27 15:36 ` [PATCH RFC 02/18] dt-bindings: vendor-prefixes: add Zhihe Han Gao via B4 Relay
2026-10-27 15:36 ` [PATCH RFC 03/18] riscv: add Zhihe A210 support Han Gao via B4 Relay
2026-10-27 15:36 ` [PATCH RFC 04/18] dt-bindings: mailbox: add the A210 AP to E902 doorbell Han Gao via B4 Relay
2026-10-27 15:36 ` [PATCH RFC 05/18] mailbox: add A210 AP to E902 doorbell support Han Gao via B4 Relay
2026-10-27 15:36 ` [PATCH RFC 06/18] dt-bindings: pinctrl: add Zhihe A210 pin controller Han Gao via B4 Relay
2026-10-27 15:36 ` [PATCH RFC 07/18] pinctrl: zhihe: add A210 support Han Gao via B4 Relay
2026-10-27 15:36 ` [PATCH RFC 08/18] dt-bindings: interrupt-controller: add Zhihe A210 PLIC Han Gao via B4 Relay
2026-10-27 15:37 ` [PATCH RFC 09/18] dt-bindings: riscv: add Melon Pi V1 and V2 Han Gao via B4 Relay
2026-10-27 15:37 ` [PATCH RFC 10/18] dt-bindings: timer: add Zhihe A210 CLINT Han Gao via B4 Relay
2026-10-27 15:37 ` [PATCH RFC 11/18] dt-bindings: firmware: add A210 SCMI clock and reset IDs Han Gao via B4 Relay
2026-10-27 15:37 ` [PATCH RFC 12/18] dt-bindings: serial: snps-dw-apb-uart: add Zhihe A210 UART Han Gao via B4 Relay
2026-10-27 15:37 ` [PATCH RFC 13/18] riscv: dts: zhihe: add A210 core support Han Gao via B4 Relay
2026-10-27 15:37 ` [PATCH RFC 14/18] riscv: dts: zhihe: add A210 UARTs Han Gao via B4 Relay
2026-10-27 15:37 ` [PATCH RFC 15/18] riscv: dts: zhihe: add A210 module memory Han Gao via B4 Relay
2026-10-27 15:37 ` [PATCH RFC 16/18] riscv: dts: zhihe: add Melon Pi V1 and V2 Han Gao via B4 Relay
2026-10-27 15:37 ` [PATCH RFC 17/18] riscv: defconfig: enable A210 support Han Gao via B4 Relay
2026-10-27 15:37 ` [PATCH RFC 18/18] MAINTAINERS: add Zhihe A210 Han Gao via B4 Relay
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d38c4a5-1a12-4af1-ac2e-413a457ce4c5@amd.com \
--to=michal.simek@amd.com \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=arm-scmi@vger.kernel.org \
--cc=bmasney+clk@redhat.com \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cristian.marussi@arm.com \
--cc=daniel.lezcano@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fustini@kernel.org \
--cc=gaohan@iscas.ac.cn \
--cc=gregkh@linuxfoundation.org \
--cc=inochiama@gmail.com \
--cc=jassisinghbrar@gmail.com \
--cc=jbrunet+clk@baylibre.com \
--cc=jiaxun.yang@flygoat.com \
--cc=jirislaby@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=me@ziyao.cc \
--cc=p.zabel@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pjw@kernel.org \
--cc=radu@rendec.net \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
--cc=sboyd@kernel.org \
--cc=sudeep.holla@kernel.org \
--cc=tglx@kernel.org \
--cc=uwu@icenowy.me \
--cc=wangruikang@iscas.ac.cn \
--cc=zhiguo.zhu@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®