From: Rob Herring <robh@kernel.org>
To: peng.fan@oss.nxp.com
Cc: ohad@wizery.com, bjorn.andersson@linaro.org,
mathieu.poirier@linaro.org, o.rempel@pengutronix.de,
devicetree@vger.kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-remoteproc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, paul@crapouillou.net,
matthias.bgg@gmail.com, agross@kernel.org,
patrice.chotard@st.com, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH V12 02/10] dt-bindings: remoteproc: imx_rproc: add i.MX8MQ/M support
Date: Fri, 5 Mar 2021 16:39:03 -0600 [thread overview]
Message-ID: <20210305223903.GA769908@robh.at.kernel.org> (raw)
In-Reply-To: <1613611500-12414-3-git-send-email-peng.fan@oss.nxp.com>
On Thu, Feb 18, 2021 at 09:24:52AM +0800, peng.fan@oss.nxp.com wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Add i.MX8MQ/M support, also include mailbox for rpmsg/virtio usage.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> .../bindings/remoteproc/fsl,imx-rproc.yaml | 51 ++++++++++++++++++-
> 1 file changed, 50 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> index 54d2456530a6..52c8e523506d 100644
> --- a/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> +++ b/Documentation/devicetree/bindings/remoteproc/fsl,imx-rproc.yaml
> @@ -4,7 +4,7 @@
> $id: "http://devicetree.org/schemas/remoteproc/fsl,imx-rproc.yaml#"
> $schema: "http://devicetree.org/meta-schemas/core.yaml#"
>
> -title: NXP iMX6SX/iMX7D Co-Processor Bindings
> +title: NXP i.MX Co-Processor Bindings
>
> description:
> This binding provides support for ARM Cortex M4 Co-processor found on some NXP iMX SoCs.
> @@ -15,6 +15,8 @@ maintainers:
> properties:
> compatible:
> enum:
> + - fsl,imx8mq-cm4
> + - fsl,imx8mm-cm4
> - fsl,imx7d-cm4
> - fsl,imx6sx-cm4
>
> @@ -26,6 +28,20 @@ properties:
> description:
> Phandle to syscon block which provide access to System Reset Controller
>
> + mbox-names:
> + items:
> + - const: tx
> + - const: rx
> + - const: rxdb
> +
> + mboxes:
> + description:
> + This property is required only if the rpmsg/virtio functionality is used.
> + List of <&phandle type channel> - 1 channel for TX, 1 channel for RX, 1 channel for RXDB.
> + (see mailbox/fsl,mu.yaml)
> + minItems: 1
> + maxItems: 3
> +
> memory-region:
> description:
> If present, a phandle for a reserved memory area that used for vdev buffer,
> @@ -58,4 +74,37 @@ examples:
> clocks = <&clks IMX7D_ARM_M4_ROOT_CLK>;
> };
>
> + - |
> + #include <dt-bindings/clock/imx8mm-clock.h>
> + rsc_table: rsc_table@550ff000 {
> + no-map;
> + reg = <0x550ff000 0x1000>;
> + };
> +
> + vdev0vring0: vdev0vring0@55000000 {
> + no-map;
> + reg = <0x55000000 0x8000>;
> + };
> +
> + vdev0vring1: vdev0vring1@55008000 {
> + reg = <0x55008000 0x8000>;
> + no-map;
> + };
> +
> + vdev0buffer: vdev0buffer@55400000 {
> + compatible = "shared-dma-pool";
> + reg = <0x55400000 0x100000>;
> + no-map;
> + };
These all go in /reserved-memory, right? Best to omit them from the
example.
> +
> + imx8mm-cm4 {
> + compatible = "fsl,imx8mm-cm4";
> + clocks = <&clk IMX8MM_CLK_M4_DIV>;
> + mbox-names = "tx", "rx", "rxdb";
> + mboxes = <&mu 0 1
> + &mu 1 1
> + &mu 3 1>;
> + memory-region = <&vdev0buffer>, <&vdev0vring0>, <&vdev0vring1>, <&rsc_table>;
> + syscon = <&src>;
> + };
> ...
> --
> 2.30.0
>
next prev parent reply other threads:[~2021-03-05 22:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 1:24 [PATCH V12 00/10] remoteproc: imx_rproc: support iMX8MQ/M peng.fan
2021-02-18 1:24 ` [PATCH V12 01/10] dt-bindings: remoteproc: convert imx rproc bindings to json-schema peng.fan
2021-03-03 6:53 ` Peng Fan (OSS)
2021-03-05 22:36 ` Rob Herring
2021-03-05 22:37 ` Rob Herring
2021-02-18 1:24 ` [PATCH V12 02/10] dt-bindings: remoteproc: imx_rproc: add i.MX8MQ/M support peng.fan
2021-03-05 22:39 ` Rob Herring [this message]
2021-02-18 1:24 ` [PATCH V12 03/10] remoteproc: introduce is_iomem to rproc_mem_entry peng.fan
2021-02-18 1:24 ` [PATCH V12 04/10] remoteproc: add is_iomem to da_to_va peng.fan
2021-02-18 3:21 ` kernel test robot
2021-02-18 1:24 ` [PATCH V12 05/10] remoteproc: imx_rproc: correct err message peng.fan
2021-02-18 1:24 ` [PATCH V12 06/10] remoteproc: imx_rproc: use devm_ioremap peng.fan
2021-02-18 1:24 ` [PATCH V12 07/10] remoteproc: imx_rproc: add i.MX specific parse fw hook peng.fan
2021-02-18 15:07 ` kernel test robot
2021-02-18 1:24 ` [PATCH V12 08/10] remoteproc: imx_rproc: support i.MX8MQ/M peng.fan
2021-02-18 1:24 ` [PATCH V12 09/10] remoteproc: imx_rproc: ignore mapping vdev regions peng.fan
2021-02-18 1:25 ` [PATCH V12 10/10] remoteproc: imx_proc: enable virtio/mailbox 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=20210305223903.GA769908@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--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=matthias.bgg@gmail.com \
--cc=o.rempel@pengutronix.de \
--cc=ohad@wizery.com \
--cc=patrice.chotard@st.com \
--cc=paul@crapouillou.net \
--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).