All of lore.kernel.org
 help / color / mirror / Atom feed
From: peng.fan@nxp.com
To: shawnguo@kernel.org, fabio.estevam@nxp.com,
	kernel@pengutronix.de, aisheng.dong@nxp.com, robh+dt@kernel.org,
	sboyd@kernel.org, linux@rempel-privat.de,
	jaswinder.singh@linaro.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-imx@nxp.com,
	leonard.crestez@nxp.com, daniel.baluta@nxp.com,
	l.stach@pengutronix.de, devicetree@vger.kernel.org,
	linux-clk@vger.kernel.org, Peng Fan <peng.fan@nxp.com>
Subject: [PATCH V3 1/3] dt-bindings: mailbox: imx-mu: support i.MX8M
Date: Mon,  1 Jun 2020 16:20:00 +0800	[thread overview]
Message-ID: <1590999602-29482-2-git-send-email-peng.fan@nxp.com> (raw)
In-Reply-To: <1590999602-29482-1-git-send-email-peng.fan@nxp.com>

From: Peng Fan <peng.fan@nxp.com>

Add i.MX8MQ/M/N/P compatible string to support i.MX8M SoCs

Reviewed-by: Dong Aisheng <aisheng.dong@nxp.com>
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
 Documentation/devicetree/bindings/mailbox/fsl,mu.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/mailbox/fsl,mu.txt b/Documentation/devicetree/bindings/mailbox/fsl,mu.txt
index 26b7a88c2fea..906377acf2cd 100644
--- a/Documentation/devicetree/bindings/mailbox/fsl,mu.txt
+++ b/Documentation/devicetree/bindings/mailbox/fsl,mu.txt
@@ -18,7 +18,8 @@ Messaging Unit Device Node:
 Required properties:
 -------------------
 - compatible :	should be "fsl,<chip>-mu", the supported chips include
-		imx6sx, imx7s, imx8qxp, imx8qm.
+		imx6sx, imx7s, imx8qxp, imx8qm, imx8mq, imx8mm, imx8mn,
+		imx8mp.
 		The "fsl,imx6sx-mu" compatible is seen as generic and should
 		be included together with SoC specific compatible.
 		There is a version 1.0 MU on imx7ulp, use "fsl,imx7ulp-mu"
-- 
2.16.4


WARNING: multiple messages have this Message-ID (diff)
From: peng.fan@nxp.com
To: shawnguo@kernel.org, fabio.estevam@nxp.com,
	kernel@pengutronix.de, aisheng.dong@nxp.com, robh+dt@kernel.org,
	sboyd@kernel.org, linux@rempel-privat.de,
	jaswinder.singh@linaro.org
Cc: devicetree@vger.kernel.org, Peng Fan <peng.fan@nxp.com>,
	linux-kernel@vger.kernel.org, linux-imx@nxp.com,
	leonard.crestez@nxp.com, daniel.baluta@nxp.com,
	linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	l.stach@pengutronix.de
Subject: [PATCH V3 1/3] dt-bindings: mailbox: imx-mu: support i.MX8M
Date: Mon,  1 Jun 2020 16:20:00 +0800	[thread overview]
Message-ID: <1590999602-29482-2-git-send-email-peng.fan@nxp.com> (raw)
In-Reply-To: <1590999602-29482-1-git-send-email-peng.fan@nxp.com>

From: Peng Fan <peng.fan@nxp.com>

Add i.MX8MQ/M/N/P compatible string to support i.MX8M SoCs

Reviewed-by: Dong Aisheng <aisheng.dong@nxp.com>
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
 Documentation/devicetree/bindings/mailbox/fsl,mu.txt | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/mailbox/fsl,mu.txt b/Documentation/devicetree/bindings/mailbox/fsl,mu.txt
index 26b7a88c2fea..906377acf2cd 100644
--- a/Documentation/devicetree/bindings/mailbox/fsl,mu.txt
+++ b/Documentation/devicetree/bindings/mailbox/fsl,mu.txt
@@ -18,7 +18,8 @@ Messaging Unit Device Node:
 Required properties:
 -------------------
 - compatible :	should be "fsl,<chip>-mu", the supported chips include
-		imx6sx, imx7s, imx8qxp, imx8qm.
+		imx6sx, imx7s, imx8qxp, imx8qm, imx8mq, imx8mm, imx8mn,
+		imx8mp.
 		The "fsl,imx6sx-mu" compatible is seen as generic and should
 		be included together with SoC specific compatible.
 		There is a version 1.0 MU on imx7ulp, use "fsl,imx7ulp-mu"
-- 
2.16.4


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-06-01  8:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01  8:19 [PATCH V3 0/3] imx8m: add mu support peng.fan
2020-06-01  8:19 ` peng.fan
2020-06-01  8:20 ` peng.fan [this message]
2020-06-01  8:20   ` [PATCH V3 1/3] dt-bindings: mailbox: imx-mu: support i.MX8M peng.fan
2020-06-02  5:24   ` Oleksij Rempel
2020-06-02  5:24     ` Oleksij Rempel
2020-06-02  5:26     ` Peng Fan
2020-06-02  5:26       ` Peng Fan
2020-06-03  3:10   ` Peng Fan
2020-06-03  3:10     ` Peng Fan
2020-06-01  8:20 ` [PATCH V3 2/3] arm64: dts: imx8m: add mu node peng.fan
2020-06-01  8:20   ` peng.fan
2020-06-01  9:44   ` Aisheng Dong
2020-06-01  9:44     ` Aisheng Dong
2020-06-23  6:50   ` Shawn Guo
2020-06-01  8:20 ` [PATCH V3 3/3] clk: imx8mp: add mu root clk peng.fan
2020-06-01  8:20   ` peng.fan
2020-06-23  6:53   ` Shawn Guo

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=1590999602-29482-2-git-send-email-peng.fan@nxp.com \
    --to=peng.fan@nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=daniel.baluta@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=jaswinder.singh@linaro.org \
    --cc=kernel@pengutronix.de \
    --cc=l.stach@pengutronix.de \
    --cc=leonard.crestez@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --cc=robh+dt@kernel.org \
    --cc=sboyd@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.