From: Peng Fan <peng.fan@oss.nxp.com>
To: Daniel Baluta <daniel.baluta@gmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.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>,
Iuliana Prodan <iuliana.prodan@nxp.com>,
Daniel Baluta <daniel.baluta@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 v2 1/3] dt-bindings: remoteproc: fsl,imx-rproc: Add support for i.MX95
Date: Tue, 17 Jun 2025 10:36:46 +0800 [thread overview]
Message-ID: <20250617023646.GA30636@nxa18884-linux> (raw)
In-Reply-To: <CAEnQRZCQj5b9GSb=i2cTn4YKtAsQPTwJ6DkiqaZjmrmboim-8A@mail.gmail.com>
Hi Daniel,
On Mon, Jun 16, 2025 at 04:07:02PM +0300, Daniel Baluta wrote:
>On Fri, Jun 6, 2025 at 4:57???AM Peng Fan (OSS) <peng.fan@oss.nxp.com> wrote:
>>
>> From: Peng Fan <peng.fan@nxp.com>
>>
>> i.MX95 has a System Manager(SM) core runs the System Control Management
>> Interface(SCMI) firmware. Vendor extenions are implemented in the
>> firmware, Logical Machine Management(LMM) protocol to manage
>> Logical Machines and CPU protocol to manage cores. The documentation
>> could be found in file drivers/firmware/arm_scmi/vendors/imx/imx95.rst.
>>
>> Add below to support i.MX95
>> - compatible string for i.MX95 M7
>> - fsl,lmm-id to indicate the LMM ID of M7 LM
>> - fsl,cpu-id to indicate the CPU ID of M7
>>
>> Signed-off-by: Peng Fan <peng.fan@nxp.com>
>> ---
>> .../bindings/remoteproc/fsl,imx-rproc.yaml | 27 ++++++++++++++++++++++
>> 1 file changed, 27 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
>> index 57d75acb0b5e52ca49d1361176fdebc18a0bf7a2..a3ffab60df52be6f1d7cf4846ca5ba1c40f03bde 100644
>> --- a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
>> +++ b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
>> @@ -28,6 +28,7 @@ properties:
>> - fsl,imx8qxp-cm4
>> - fsl,imx8ulp-cm33
>> - fsl,imx93-cm33
>> + - fsl,imx95-cm7
>>
>> clocks:
>> maxItems: 1
>> @@ -68,6 +69,12 @@ properties:
>> Indicate whether need to load the default firmware and start the remote
>> processor automatically.
>>
>> + fsl,cpu-id:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description:
>> + This property is to specify the CPU ID of the remote processor
>> + in SoC which supports System Manager
>> +
>> fsl,entry-address:
>> $ref: /schemas/types.yaml#/definitions/uint32
>> description:
>> @@ -78,6 +85,12 @@ properties:
>> description:
>> Phandle to IOMUXC GPR block which provide access to CM7 CPUWAIT bit.
>>
>> + fsl,lmm-id:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description:
>> + This property is to specify the Logical Machine ID of the remote processor
>> + in SoC which supports System Manager
>> +
>> fsl,resource-id:
>> $ref: /schemas/types.yaml#/definitions/uint32
>> description:
>> @@ -114,6 +127,20 @@ allOf:
>> properties:
>> power-domains: false
>>
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + const: fsl,imx95-cm7
>> + then:
>> + required:
>> + - fsl,lmm-id
>> + - fsl,cpu-id
>> + else:
>> + properties:
>> + fsl,lmm-id: false
>> + fsl,cpu-id: false
>
>Hi Peng,
>
>Can you remind me why do we need the else branch here?
>
>I mean if the compatible is not fsl,imx95-cm7 then the properties
>fsl,lmm-id and fsl,cpu-id are not required and I think that's fine.
It is not required, but we should also block others wrongly add
the properties. Such as dt-schema should report error if user wrongly add
these properties in DTS.
DT maintainers may help comment more.
Thanks,
Peng
next prev parent reply other threads:[~2025-06-17 1:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 1:55 [PATCH v2 0/3] remoteproc: imx_rproc: Support i.MX95 Peng Fan (OSS)
2025-06-06 1:55 ` [PATCH v2 1/3] dt-bindings: remoteproc: fsl,imx-rproc: Add support for i.MX95 Peng Fan (OSS)
2025-06-16 13:07 ` Daniel Baluta
2025-06-17 2:36 ` Peng Fan [this message]
2025-06-23 14:47 ` Krzysztof Kozlowski
2025-06-24 12:00 ` Peng Fan
2025-06-06 1:55 ` [PATCH v2 2/3] remoteproc: imx_rproc: Add support for System Manager API Peng Fan (OSS)
2025-06-09 15:17 ` Mathieu Poirier
2025-06-16 13:32 ` Daniel Baluta
2025-06-06 1:55 ` [PATCH v2 3/3] remoteproc: imx_rproc: Add support for i.MX95 Peng Fan (OSS)
2025-06-19 8:54 ` [PATCH v2 0/3] remoteproc: imx_rproc: Support i.MX95 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=20250617023646.GA30636@nxa18884-linux \
--to=peng.fan@oss.nxp.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@gmail.com \
--cc=daniel.baluta@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.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=mathieu.poirier@linaro.org \
--cc=peng.fan@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