From: Rob Herring <robh@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: bjorn.andersson@linaro.org, mathieu.poirier@linaro.org,
krzysztof.kozlowski@canonical.com, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
linux-remoteproc@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH V2 2/6] dt-bindings: remoteproc: imx_rproc: support i.MX8QM
Date: Thu, 10 Mar 2022 17:09:27 -0600 [thread overview]
Message-ID: <YiqFJ+1l/h7XCQkN@robh.at.kernel.org> (raw)
In-Reply-To: <20220309102118.8131-3-peng.fan@oss.nxp.com>
On Wed, Mar 09, 2022 at 06:21:14PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Add i.MX8QM compatible
>
> There are two general purpose M4, so add reg property to indicate the
> id.
Where does the id come from? Is this just an index?
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> .../devicetree/bindings/remoteproc/fsl,imx-rproc.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> index f25c203dd2f9..41d366cff3cd 100644
> --- a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> +++ b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> @@ -20,6 +20,7 @@ properties:
> - fsl,imx8mn-cm7
> - fsl,imx8mp-cm7
> - fsl,imx8qxp-cm4
> + - fsl,imx8qm-cm4
> - fsl,imx8ulp-cm33
> - fsl,imx7d-cm4
> - fsl,imx7ulp-cm4
> @@ -68,6 +69,9 @@ properties:
> power-domains:
> maxItems: 8
>
> + reg:
> + maxItems: 1
> +
> rsrc-id:
> description:
> This property is to specify the resource id of the remote processor in SoC
> --
> 2.30.0
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-10 23:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 10:21 [PATCH V2 0/6] remoteproc: imx_rproc: support i.MX8QM/QXP Peng Fan (OSS)
2022-03-09 10:21 ` [PATCH V2 1/6] dt-bindings: remoteproc: imx_rproc: support i.MX8QXP Peng Fan (OSS)
2022-03-09 17:18 ` Krzysztof Kozlowski
2022-03-11 1:59 ` Peng Fan
2022-03-09 10:21 ` [PATCH V2 2/6] dt-bindings: remoteproc: imx_rproc: support i.MX8QM Peng Fan (OSS)
2022-03-10 23:09 ` Rob Herring [this message]
2022-03-11 1:58 ` Peng Fan
2022-03-14 22:38 ` Bjorn Andersson
2022-03-09 10:21 ` [PATCH V2 3/6] remoteproc: imx_rproc: support attaching to i.MX8QXP M4 Peng Fan (OSS)
2022-03-09 10:21 ` [PATCH V2 4/6] remoteproc: imx_rproc: support kicking Mcore from Linux for i.MX8QXP Peng Fan (OSS)
2022-03-09 10:21 ` [PATCH V2 5/6] remoteproc: imx_rproc: support i.MX8QM Peng Fan (OSS)
2022-03-09 10:21 ` [PATCH V2 6/6] remoteproc: imx_rproc: request mbox channel later Peng Fan (OSS)
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=YiqFJ+1l/h7XCQkN@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.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).