From: Cristian Marussi <cristian.marussi@arm.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"arm-scmi@vger.kernel.org" <arm-scmi@vger.kernel.org>,
"sudeep.holla@arm.com" <sudeep.holla@arm.com>,
"james.quinlan@broadcom.com" <james.quinlan@broadcom.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
"etienne.carriere@st.com" <etienne.carriere@st.com>,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
"michal.simek@amd.com" <michal.simek@amd.com>,
"quic_sibis@quicinc.com" <quic_sibis@quicinc.com>,
"quic_nkela@quicinc.com" <quic_nkela@quicinc.com>,
"ptosi@google.com" <ptosi@google.com>,
"dan.carpenter@linaro.org" <dan.carpenter@linaro.org>,
"souvik.chakravarty@arm.com" <souvik.chakravarty@arm.com>,
Etienne Carriere <etienne.carriere@foss.st.com>
Subject: Re: [PATCH v2 6/8] firmware: arm_scmi: Make OPTEE transport a standalone driver
Date: Thu, 11 Jul 2024 15:20:41 +0100 [thread overview]
Message-ID: <Zo_qOcRa11INO8cs@pluto> (raw)
In-Reply-To: <PAXPR04MB8459B0299D11F08605C20BB988A52@PAXPR04MB8459.eurprd04.prod.outlook.com>
On Thu, Jul 11, 2024 at 12:57:46PM +0000, Peng Fan wrote:
> > Subject: [PATCH v2 6/8] firmware: arm_scmi: Make OPTEE transport a
> > standalone driver
> >
> > Make SCMI OPTEE transport a standalone driver that can be optionally
> > loaded as a module.
> >
> > CC: Etienne Carriere <etienne.carriere@foss.st.com>
> > Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
> > ---
> > v1 --> v2
> > - handle platform_driver_register() failures
> > ---
> > drivers/firmware/arm_scmi/Kconfig | 6 +-
> > drivers/firmware/arm_scmi/Makefile | 2 +-
> > drivers/firmware/arm_scmi/common.h | 3 -
> > drivers/firmware/arm_scmi/driver.c | 3 -
> > .../{optee.c => scmi_transport_optee.c} | 91 ++++++++++---------
> > 5 files changed, 52 insertions(+), 53 deletions(-) rename
> > drivers/firmware/arm_scmi/{optee.c => scmi_transport_optee.c} (90%)
> >
> > diff --git a/drivers/firmware/arm_scmi/Kconfig
> > b/drivers/firmware/arm_scmi/Kconfig
> > index a4d44ef8bf45..def7e3f09356 100644
> > --- a/drivers/firmware/arm_scmi/Kconfig
> > +++ b/drivers/firmware/arm_scmi/Kconfig
> > @@ -89,8 +89,8 @@ config ARM_SCMI_TRANSPORT_MAILBOX
> > will be called scmi_transport_mailbox.
> >
> > config ARM_SCMI_TRANSPORT_OPTEE
> > - bool "SCMI transport based on OP-TEE service"
> > - depends on OPTEE=y || OPTEE=ARM_SCMI_PROTOCOL
> > + tristate "SCMI transport based on OP-TEE service"
> > + depends on OPTEE
> > select ARM_SCMI_HAVE_TRANSPORT
> > select ARM_SCMI_HAVE_SHMEM
> > select ARM_SCMI_HAVE_MSG
> > @@ -100,6 +100,8 @@ config ARM_SCMI_TRANSPORT_OPTEE
> >
> > If you want the ARM SCMI PROTOCOL stack to include
> > support for a
> > transport based on OP-TEE SCMI service, answer Y.
> > + This driver can also be built as a module. If so, the module
> > + will be called scmi_transport_optee.
> >
> > config ARM_SCMI_TRANSPORT_SMC
> > tristate "SCMI transport based on SMC"
> > diff --git a/drivers/firmware/arm_scmi/Makefile
> > b/drivers/firmware/arm_scmi/Makefile
> > index 6868a47fa4ab..b04119ce972f 100644
> > --- a/drivers/firmware/arm_scmi/Makefile
> > +++ b/drivers/firmware/arm_scmi/Makefile
> > @@ -7,13 +7,13 @@ scmi-driver-
> > $(CONFIG_ARM_SCMI_RAW_MODE_SUPPORT) += raw_mode.o
> > scmi-transport-$(CONFIG_ARM_SCMI_HAVE_SHMEM) = shmem.o
> > scmi-transport-$(CONFIG_ARM_SCMI_HAVE_MSG) += msg.o
> > scmi-transport-$(CONFIG_ARM_SCMI_TRANSPORT_VIRTIO) += virtio.o
> > -scmi-transport-$(CONFIG_ARM_SCMI_TRANSPORT_OPTEE) += optee.o
> > scmi-protocols-y := base.o clock.o perf.o power.o reset.o sensors.o
> > system.o voltage.o powercap.o scmi-protocols-y += pinctrl.o scmi-
> > module-objs := $(scmi-driver-y) $(scmi-protocols-y) $(scmi-transport-y)
> >
> > obj-$(CONFIG_ARM_SCMI_TRANSPORT_SMC) +=
> > scmi_transport_smc.o
> > obj-$(CONFIG_ARM_SCMI_TRANSPORT_MAILBOX) +=
> > scmi_transport_mailbox.o
> > +obj-$(CONFIG_ARM_SCMI_TRANSPORT_OPTEE) +=
> > scmi_transport_optee.o
> >
> > obj-$(CONFIG_ARM_SCMI_PROTOCOL) += scmi-core.o
> > obj-$(CONFIG_ARM_SCMI_PROTOCOL) += scmi-module.o diff --git
> > a/drivers/firmware/arm_scmi/common.h
> > b/drivers/firmware/arm_scmi/common.h
> > index edb786cde25c..0ce1d804b3fc 100644
> > --- a/drivers/firmware/arm_scmi/common.h
> > +++ b/drivers/firmware/arm_scmi/common.h
> > @@ -289,9 +289,6 @@ int
> > scmi_xfer_raw_wait_for_message_response(struct scmi_chan_info
> > *cinfo, #ifdef CONFIG_ARM_SCMI_TRANSPORT_VIRTIO extern const
> > struct scmi_desc scmi_virtio_desc; #endif -#ifdef
> > CONFIG_ARM_SCMI_TRANSPORT_OPTEE -extern const struct
> > scmi_desc scmi_optee_desc; -#endif
> >
> > void scmi_rx_callback(struct scmi_chan_info *cinfo, u32 msg_hdr,
> > void *priv);
> >
> > diff --git a/drivers/firmware/arm_scmi/driver.c
> > b/drivers/firmware/arm_scmi/driver.c
> > index b14c5326930a..67b416c7f2f5 100644
> > --- a/drivers/firmware/arm_scmi/driver.c
> > +++ b/drivers/firmware/arm_scmi/driver.c
> > @@ -3251,9 +3251,6 @@ ATTRIBUTE_GROUPS(versions);
> >
> > /* Each compatible listed below must have descriptor associated with
> > it */ static const struct of_device_id scmi_of_match[] = { -#ifdef
> > CONFIG_ARM_SCMI_TRANSPORT_OPTEE
> > - { .compatible = "linaro,scmi-optee", .data =
> > &scmi_optee_desc },
> > -#endif
> > #ifdef CONFIG_ARM_SCMI_TRANSPORT_VIRTIO
> > { .compatible = "arm,scmi-virtio", .data = &scmi_virtio_desc},
> > #endif diff --git a/drivers/firmware/arm_scmi/optee.c
> > b/drivers/firmware/arm_scmi/scmi_transport_optee.c
> > similarity index 90%
> > rename from drivers/firmware/arm_scmi/optee.c rename to
> > drivers/firmware/arm_scmi/scmi_transport_optee.c
> > index 99f3b0bfb956..7a16c8d3e213 100644
> > --- a/drivers/firmware/arm_scmi/optee.c
> > +++ b/drivers/firmware/arm_scmi/scmi_transport_optee.c
> > @@ -1,6 +1,6 @@
> > // SPDX-License-Identifier: GPL-2.0
> > /*
> > - * Copyright (C) 2019-2021 Linaro Ltd.
> > + * Copyright (C) 2019-2024 Linaro Ltd.
>
> This should be kept unchanged?
Not sure, like I said previously, how to go about years.
Thanks,
Cristian
next prev parent reply other threads:[~2024-07-11 14:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 17:31 [PATCH 0/8] Make SCMI transport as standalone drivers Cristian Marussi
2024-07-10 17:31 ` [PATCH v2 1/8] firmware: arm_scmi: Introduce setup_shmem_iomap Cristian Marussi
2024-07-12 19:44 ` kernel test robot
2024-07-26 15:18 ` Cristian Marussi
2024-07-10 17:31 ` [PATCH v2 2/8] firmware: arm_scmi: Introduce packet handling helpers Cristian Marussi
2024-07-11 10:43 ` Peng Fan
2024-07-11 14:08 ` Cristian Marussi
2024-07-23 13:41 ` Etienne CARRIERE
2024-07-26 14:57 ` Cristian Marussi
2024-07-10 17:31 ` [PATCH v2 3/8] firmware: arm_scmi: Add support for standalone transport drivers Cristian Marussi
2024-07-11 12:54 ` Peng Fan
2024-07-11 14:18 ` Cristian Marussi
2024-07-23 13:39 ` Etienne CARRIERE
2024-07-26 14:59 ` Cristian Marussi
2024-07-10 17:31 ` [PATCH v2 4/8] firmware: arm_scmi: Make MBOX transport a standalone driver Cristian Marussi
2024-07-11 12:56 ` Peng Fan
2024-07-23 13:41 ` Etienne CARRIERE
2024-07-26 15:00 ` Cristian Marussi
2024-07-10 17:31 ` [PATCH v2 5/8] firmware: arm_scmi: Make SMC " Cristian Marussi
2024-07-10 21:04 ` Nikunj Kela
2024-07-11 10:09 ` Cristian Marussi
2024-07-10 17:31 ` [PATCH v2 6/8] firmware: arm_scmi: Make OPTEE " Cristian Marussi
2024-07-11 12:57 ` Peng Fan
2024-07-11 14:20 ` Cristian Marussi [this message]
2024-07-26 15:01 ` Cristian Marussi
2024-07-10 17:31 ` [PATCH v2 7/8] firmware: arm_scmi: Make VirtIO " Cristian Marussi
2024-07-10 17:31 ` [PATCH v2 8/8] firmware: arm_scmi: Remove legacy transport-layer code Cristian Marussi
2024-07-11 13:26 ` [PATCH 0/8] Make SCMI transport as standalone drivers Peng Fan
2024-07-11 14:22 ` Cristian Marussi
2024-07-23 13:36 ` Etienne CARRIERE
2024-07-26 15:14 ` Cristian Marussi
2024-07-12 21:02 ` Florian Fainelli
2024-07-26 15:17 ` Cristian Marussi
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=Zo_qOcRa11INO8cs@pluto \
--to=cristian.marussi@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=etienne.carriere@foss.st.com \
--cc=etienne.carriere@st.com \
--cc=f.fainelli@gmail.com \
--cc=james.quinlan@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=ptosi@google.com \
--cc=quic_nkela@quicinc.com \
--cc=quic_sibis@quicinc.com \
--cc=souvik.chakravarty@arm.com \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.