public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
	Cristian Marussi <cristian.marussi@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	"Pengutronix Kernel Team" <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	"Rob Herring" <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"arm-scmi@vger.kernel.org" <arm-scmi@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v4 5/7] firmware: imx: Add i.MX95 SCMI LMM driver
Date: Mon, 14 Apr 2025 11:15:17 +0100	[thread overview]
Message-ID: <20250414-tiny-classic-barnacle-5f8c8f@sudeepholla> (raw)
In-Reply-To: <PAXPR04MB8459195AAF65D38AFA1D4F9688B32@PAXPR04MB8459.eurprd04.prod.outlook.com>

On Mon, Apr 14, 2025 at 09:57:43AM +0000, Peng Fan wrote:
> Hi Sudeep,
> 
> > Subject: Re: [PATCH v4 5/7] firmware: imx: Add i.MX95 SCMI LMM
> > driver
> > 
> > On Tue, Apr 08, 2025 at 04:44:29PM +0800, Peng Fan (OSS) wrote:
> > > From: Peng Fan <peng.fan@nxp.com>
> > >
> > > The i.MX95 System manager exports SCMI LMM protocol for linux to
> > > manage Logical Machines. The driver is to use the LMM Protocol
> > > interface to boot, shutdown a LM.
> > >
> > > Reviewed-by: Cristian Marussi <cristian.marussi@arm.com>
> > > Signed-off-by: Peng Fan <peng.fan@nxp.com>
> > > ---
> > >  drivers/firmware/arm_scmi/vendors/imx/Kconfig |  3 +-
> > >  drivers/firmware/imx/Kconfig                  | 11 ++++
> > >  drivers/firmware/imx/Makefile                 |  1 +
> > >  drivers/firmware/imx/sm-lmm.c                 | 91
> > +++++++++++++++++++++++++++
> > >  include/linux/firmware/imx/sm.h               | 14 +++++
> > >  5 files changed, 119 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/firmware/arm_scmi/vendors/imx/Kconfig
> > > b/drivers/firmware/arm_scmi/vendors/imx/Kconfig
> > > index
> > >
> > b5f13d0e40155e485f4d1696e9550645d888ef44..4c24e17425f83081
> > 0f8ba376ece9
> > > db93c8cded6d 100644
> > > --- a/drivers/firmware/arm_scmi/vendors/imx/Kconfig
> > > +++ b/drivers/firmware/arm_scmi/vendors/imx/Kconfig
> > > @@ -26,7 +26,8 @@ config IMX_SCMI_CPU_EXT  config
> > IMX_SCMI_LMM_EXT
> > >  	tristate "i.MX SCMI LMM EXTENSION"
> > >  	depends on ARM_SCMI_PROTOCOL || (COMPILE_TEST && OF)
> > > -	default y if ARCH_MXC
> > > +	depends on IMX_SCMI_LMM_DRV
> > > +	default y if ARCH_MXC && ARM64
> > 
> > I can't understand the ARM64 dependency on this and next patch.
> 
> ARCH_MXC both supports ARM32 and ARM64.
> 
> To i.MX ARM32 platform, there is no plan to enable SCMI, so only
> set y for ARCH_MXC ARM64 platforms.
> 

OK but why is it different for IMX_SCMI_MISC_DRV. I really don't see
any dependency. If it is not supported today fine, but do you need any
issue to use it or compile it for arm32 ?

-- 
Regards,
Sudeep


  reply	other threads:[~2025-04-14 10:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08  8:44 [PATCH v4 0/7] firmware: scmi/imx: Add i.MX95 LMM/CPU Protocol Peng Fan (OSS)
2025-04-08  8:44 ` [PATCH v4 1/7] firmware: arm_scmi: imx: Add LMM and CPU documentation Peng Fan (OSS)
2025-04-08  8:44 ` [PATCH v4 2/7] dt-bindings: firmware: Add i.MX95 SCMI LMM and CPU protocol Peng Fan (OSS)
2025-04-08  8:44 ` [PATCH v4 3/7] firmware: arm_scmi: imx: Add i.MX95 LMM protocol Peng Fan (OSS)
2025-04-08  9:17   ` Dan Carpenter
2025-04-09  3:37     ` Peng Fan
2025-04-08  9:21   ` Dan Carpenter
2025-04-09  3:33     ` Peng Fan
2025-04-08  8:44 ` [PATCH v4 4/7] firmware: arm_scmi: imx: Add i.MX95 CPU Protocol Peng Fan (OSS)
2025-04-08  8:44 ` [PATCH v4 5/7] firmware: imx: Add i.MX95 SCMI LMM driver Peng Fan (OSS)
2025-04-14  9:34   ` Sudeep Holla
2025-04-14  9:57     ` Peng Fan
2025-04-14 10:15       ` Sudeep Holla [this message]
2025-04-14 10:44         ` Peng Fan
2025-04-14 11:00           ` Peng Fan
2025-04-14 11:17             ` Sudeep Holla
2025-04-15  9:10               ` Peng Fan
2025-04-15 14:48                 ` Sudeep Holla
2025-04-08  8:44 ` [PATCH v4 6/7] firmware: imx: Add i.MX95 SCMI CPU driver Peng Fan (OSS)
2025-04-08  8:44 ` [PATCH v4 7/7] MAINTAINERS: add entry for i.MX SCMI extensions Peng Fan (OSS)
2025-04-24  9:43 ` [PATCH v4 0/7] firmware: scmi/imx: Add i.MX95 LMM/CPU Protocol Sudeep Holla

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=20250414-tiny-classic-barnacle-5f8c8f@sudeepholla \
    --to=sudeep.holla@arm.com \
    --cc=arm-scmi@vger.kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=cristian.marussi@arm.com \
    --cc=dan.carpenter@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=peng.fan@oss.nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.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