From: Cristian Marussi <cristian.marussi@arm.com>
To: Etienne CARRIERE <etienne.carriere@st.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>,
"peng.fan@oss.nxp.com" <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>
Subject: Re: [PATCH v2 4/8] firmware: arm_scmi: Make MBOX transport a standalone driver
Date: Fri, 26 Jul 2024 16:00:51 +0100 [thread overview]
Message-ID: <ZqO6IyaOaTbuQBOd@pluto> (raw)
In-Reply-To: <PAXPR10MB46879DC8AB435367E0D3C251FDA92@PAXPR10MB4687.EURPRD10.PROD.OUTLOOK.COM>
On Tue, Jul 23, 2024 at 01:41:04PM +0000, Etienne CARRIERE wrote:
> Hi Cristian,
>
> On Wednesday, July 10, 2024, Cristian Marussi wrote:
> > Make SCMI mailbox transport a standalne driver that can be optionally
> > loaded as a module.
> >
> > Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
> > ---
> > drivers/firmware/arm_scmi/Kconfig | 4 +-
> > drivers/firmware/arm_scmi/Makefile | 3 +-
> > drivers/firmware/arm_scmi/common.h | 3 --
> > drivers/firmware/arm_scmi/driver.c | 3 --
> > .../{mailbox.c => scmi_transport_mailbox.c} | 44 +++++++++++++------
> > 5 files changed, 36 insertions(+), 21 deletions(-)
> > rename drivers/firmware/arm_scmi/{mailbox.c => scmi_transport_mailbox.c} (88%)
> >
> > diff --git a/drivers/firmware/arm_scmi/Kconfig b/drivers/firmware/arm_scmi/Kconfig
> > index aa5842be19b2..135e34aefd70 100644
> > --- a/drivers/firmware/arm_scmi/Kconfig
> > +++ b/drivers/firmware/arm_scmi/Kconfig
> > @@ -75,7 +75,7 @@ config ARM_SCMI_HAVE_MSG
> > available.
> >
> > config ARM_SCMI_TRANSPORT_MAILBOX
> > - bool "SCMI transport based on Mailbox"
> > + tristate "SCMI transport based on Mailbox"
> > depends on MAILBOX
> > select ARM_SCMI_HAVE_TRANSPORT
> > select ARM_SCMI_HAVE_SHMEM
> > @@ -85,6 +85,8 @@ config ARM_SCMI_TRANSPORT_MAILBOX
> >
> > If you want the ARM SCMI PROTOCOL stack to include support for a
> > transport based on mailboxes, answer Y.
> > + This driver can also be built as a module. If so, the module
>
> Nitpicking: replace the 2 space char before "if so," with a single one?
> Applies also to patch 5/8, 6/8 and 7/8.
>
Fixed in V3.
> Other wise LGTM , but my comment on patch 3/8 that would affect
> use of DEFINE_SCMI_TRANSPORT_DRIVER() in patch 5 to 7.
>
Yes I reworked the macros params.
Thanks,
Cristian
next prev parent reply other threads:[~2024-07-26 15:01 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 [this message]
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
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=ZqO6IyaOaTbuQBOd@pluto \
--to=cristian.marussi@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=dan.carpenter@linaro.org \
--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@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).