From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Peng Fan <peng.fan@oss.nxp.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Frank Li <frank.li@nxp.com>,
Daniel Baluta <daniel.baluta@nxp.com>,
Iuliana Prodan <iuliana.prodan@nxp.com>,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH v3 3/5] remoteproc: imx_rproc: Add support for i.MX95
Date: Wed, 9 Jul 2025 08:31:48 -0600 [thread overview]
Message-ID: <aG59VPhYY5deFo_h@p14s> (raw)
In-Reply-To: <20250709074940.GA14535@nxa18884-linux>
On Wed, Jul 09, 2025 at 03:49:40PM +0800, Peng Fan wrote:
> Hi Mathieu,
>
> On Tue, Jul 08, 2025 at 10:39:55AM -0600, Mathieu Poirier wrote:
> >On Wed, Jun 25, 2025 at 10:23:29AM +0800, Peng Fan (OSS) wrote:
> >> From: Peng Fan <peng.fan@nxp.com>
> >>
> >> Add imx_rproc_cfg_imx95_m7 and address(TCM and DDR) mapping.
> >> Add i.MX95 of_device_id entry.
> >>
> >> Reviewed-by: Daniel Baluta <daniel.baluta@nxp.com>
> >> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> >> ---
> >> drivers/remoteproc/imx_rproc.c | 25 +++++++++++++++++++++++++
> >> 1 file changed, 25 insertions(+)
> >>
> >> diff --git a/drivers/remoteproc/imx_rproc.c b/drivers/remoteproc/imx_rproc.c
> >> index b1a117ca5e5795554b67eb7092db2a25fc7de13b..c226f78c84ad180c69804116d6cfcab19db6aaa5 100644
> >> --- a/drivers/remoteproc/imx_rproc.c
> >> +++ b/drivers/remoteproc/imx_rproc.c
> >> @@ -73,6 +73,10 @@
> >>
> >> #define IMX_SC_IRQ_GROUP_REBOOTED 5
> >>
> >> +/* Must align with System Manager Firmware */
> >> +#define IMX95_M7_CPUID 1
> >> +#define IMX95_M7_LMID 1
> >
> >Any reason those aren't set in the device tree?
>
> Krzysztof rejected to introduce the IDs to devicetree.
>
> From IRC:
> "To me this makes no sense in current explanayton - you have 8 cores, but only
> one can be put there, so what happens with the rest?
> And I don't think we care about something like remote and local ID - it is
> the same. CPUs have single number. So this looks like copy paste downstream
> and thus solve it internally first"
>
>
> In System Manager Firmware, CPUID is fixed and will not change.
> LMID is also fixed as of now, we not expect customer to change LMID.
>
> So with "fsl,imx95-m7", we could know the CPUID and LMID for M7, so
> it does not make sense to introduce new property saying "fsl,imx95-lmid"
> and "fsl,imx95-cpuid". This should be the main concern that DT maintainers
> reject to add properties for the IDs.
>
Ok
> Thanks,
> Peng
>
> >
> >Thanks,
> >Mathieu
> >
next prev parent reply other threads:[~2025-07-09 14:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 2:23 [PATCH v3 0/5] remoteproc: imx_rproc: Support i.MX95 Peng Fan (OSS)
2025-06-25 2:23 ` [PATCH v3 1/5] dt-bindings: remoteproc: fsl,imx-rproc: Add support for i.MX95 Peng Fan (OSS)
2025-06-26 18:45 ` Frank Li
2025-06-27 7:06 ` Krzysztof Kozlowski
2025-06-25 2:23 ` [PATCH v3 2/5] remoteproc: imx_rproc: Add support for System Manager API Peng Fan (OSS)
2025-06-26 18:48 ` Frank Li
2025-07-08 16:32 ` Mathieu Poirier
2025-07-09 9:02 ` Peng Fan
2025-07-09 14:33 ` Mathieu Poirier
2025-07-09 15:01 ` Peng Fan
2025-06-25 2:23 ` [PATCH v3 3/5] remoteproc: imx_rproc: Add support for i.MX95 Peng Fan (OSS)
2025-06-26 18:50 ` Frank Li
2025-07-08 16:39 ` Mathieu Poirier
2025-07-09 7:49 ` Peng Fan
2025-07-09 14:31 ` Mathieu Poirier [this message]
2025-06-25 2:23 ` [PATCH v3 4/5] arm64: dts: imx95: Add SCMI LMM/CPU nodes Peng Fan (OSS)
2025-06-26 18:50 ` Frank Li
2025-06-25 2:23 ` [PATCH v3 5/5] arm64: dts: imx95-19x19-evk: Add CM7 nodes and vdev related memory regions Peng Fan (OSS)
2025-06-26 18:52 ` Frank Li
2025-06-27 3:21 ` Peng Fan
2025-06-25 20:25 ` [PATCH v3 0/5] remoteproc: imx_rproc: Support i.MX95 Rob Herring (Arm)
2025-06-26 3:56 ` Peng Fan
2025-07-03 5:01 ` 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=aG59VPhYY5deFo_h@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=frank.li@nxp.com \
--cc=imx@lists.linux.dev \
--cc=iuliana.prodan@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@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;
as well as URLs for NNTP newsgroup(s).