From: Sudeep Holla <sudeep.holla@arm.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
Chuck Cannon <chuck.cannon@nxp.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Cristian Marussi <cristian.marussi@arm.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
"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>
Subject: Re: [PATCH 3/5] firmware: arm_scmi: imx: Add LMM and CPU documentation
Date: Tue, 25 Feb 2025 10:21:58 +0000 [thread overview]
Message-ID: <Z72ZxspU3hfGZWez@bogus> (raw)
In-Reply-To: <PAXPR04MB8459D4C2CA3D5AE58B2B509788E02@PAXPR04MB8459.eurprd04.prod.outlook.com>
On Thu, Jan 23, 2025 at 01:30:43AM +0000, Peng Fan wrote:
>
> This is to manage the M7 core by Linux. I just put more documentation here.
> CPU protocol is also used by ATF to manage AP cores.
>
Good
> > Also what other CPUs are we talking here.
>
> M7 core
>
Are they referred by any other name in the system ? I reason I ask is using
plain "CPU" is too generic and confusing. At the same time using "M7" may be
too specific. I am trying to see if there is any middle ground.
> In general I would like to
> > explore the possibility of collapsing this with LM protocol. CPUs within
> > LM is LM's responsibility to bring up. And CPU can be seen as an LM for
> > sake of this vendor protocol. I am not get into details here yet before I
> > can understand what these CPUs are really in the system and why we
> > need this.
>
> Our system supports M7 and A55 in one LM, so A55 use CPU protocol to
> manage M7. When M7 and A55 in different LM, use LM protocol to
> manage M7 LM.
>
The LM(assuming Logical Module/Machine) is an abstract construct, it should
apply to even subset of components within an LM. Just wondering what are
specific reasons do you think applying LM protocol you have on those M7
CPUs alone in A55+M7 LM would not fit well.
--
Regards,
Sudeep
next prev parent reply other threads:[~2025-02-25 11:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 15:08 [PATCH 0/5] firmware: scmi/imx: Add i.MX95 LMM/CPU Protocol Peng Fan (OSS)
2025-01-21 15:08 ` [PATCH 1/5] firmware: arm_scmi: imx: Add i.MX95 LMM protocol Peng Fan (OSS)
2025-01-24 2:43 ` kernel test robot
2025-01-21 15:08 ` [PATCH 2/5] firmware: arm_scmi: imx: Add i.MX95 CPU Protocol Peng Fan (OSS)
2025-01-22 8:48 ` Dan Carpenter
2025-01-22 12:22 ` Cristian Marussi
2025-01-22 12:41 ` Dan Carpenter
2025-01-22 12:55 ` Cristian Marussi
2025-01-22 13:59 ` Sudeep Holla
2025-01-24 4:11 ` kernel test robot
2025-01-21 15:08 ` [PATCH 3/5] firmware: arm_scmi: imx: Add LMM and CPU documentation Peng Fan (OSS)
2025-01-22 12:14 ` Sudeep Holla
2025-01-23 1:30 ` Peng Fan
2025-02-25 10:21 ` Sudeep Holla [this message]
2025-02-25 12:42 ` Peng Fan
2025-02-25 11:49 ` Sudeep Holla
2025-02-26 3:11 ` Peng Fan
2025-01-21 15:08 ` [PATCH 4/5] firmware: imx: Add i.MX95 SCMI LMM driver Peng Fan (OSS)
2025-01-21 15:08 ` [PATCH 5/5] firmware: imx: Add i.MX95 SCMI CPU driver Peng Fan (OSS)
2025-01-21 15:31 ` [PATCH 0/5] firmware: scmi/imx: Add i.MX95 LMM/CPU Protocol Cristian Marussi
2025-01-22 5:31 ` Peng Fan
2025-01-25 1:00 ` Peng Fan
2025-02-06 2:40 ` Peng Fan
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=Z72ZxspU3hfGZWez@bogus \
--to=sudeep.holla@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=chuck.cannon@nxp.com \
--cc=cristian.marussi@arm.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--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=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;
as well as URLs for NNTP newsgroup(s).