From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Shawn Guo <shawnguo@kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"A.s. Dong" <aisheng.dong@nxp.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
dl-linux-imx <linux-imx@nxp.com>,
linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de,
devicetree@vger.kernel.org
Subject: [PATCH v4 2/4] dt-bindings: arm: fsl: rework mu doc
Date: Wed, 18 Jul 2018 09:12:49 +0200 [thread overview]
Message-ID: <20180718071251.8857-3-o.rempel@pengutronix.de> (raw)
In-Reply-To: <20180718071251.8857-1-o.rempel@pengutronix.de>
- Remove software specific description. MU has many use cases
limited only by imagination. So remove this confusing part.
- Add all currently known SoCs with MU
- Make sure this documentation covers not only Firmware specific use
case. Parameters for generic configurations should be described as well.
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
---
.../devicetree/bindings/mailbox/fsl,mu.txt | 32 +++++++++----------
1 file changed, 15 insertions(+), 17 deletions(-)
diff --git a/Documentation/devicetree/bindings/mailbox/fsl,mu.txt b/Documentation/devicetree/bindings/mailbox/fsl,mu.txt
index 90e4905dfc69..9d5e6ee61e22 100644
--- a/Documentation/devicetree/bindings/mailbox/fsl,mu.txt
+++ b/Documentation/devicetree/bindings/mailbox/fsl,mu.txt
@@ -1,28 +1,26 @@
NXP i.MX Messaging Unit (MU)
--------------------------------------------------------------------
-The Messaging Unit module enables two processors within the SoC to
-communicate and coordinate by passing messages (e.g. data, status
-and control) through the MU interface. The MU also provides the ability
-for one processor to signal the other processor using interrupts.
-
-Because the MU manages the messaging between processors, the MU uses
-different clocks (from each side of the different peripheral buses).
-Therefore, the MU must synchronize the accesses from one side to the
-other. The MU accomplishes synchronization using two sets of matching
-registers (Processor A-facing, Processor B-facing).
-
-Messaging Unit Device Node:
-=============================
-
Required properties:
-------------------
-- compatible : should be "fsl,<chip>-mu", the supported chips include
- imx8qxp, imx8qm.
+- compatible : should be "fsl,<chip>-mu", the supported chips include:
+ fsl,imx6sx-mu - i.MX 6SoloX
+ fsl,imx7d-mu - i.MX 7Dual
+ fsl,imx7s-mu - i.MX 7Solo
+ fsl,imx7ulp-mu - i.MX 7ULP
+ fsl,imx8qm-mu - i.MX 8QM
+ fsl,imx8qxp-mu - i.MX 8QXP
- reg : Should contain the registers location and length
- interrupts : Interrupt number. The interrupt specifier format depends
on the interrupt controller parent.
-- #mbox-cells: Must be 0. Number of cells in a mailbox
+- #mbox-cells: Must be:
+ 0 - for single channel mode. i.MX8* SCU protocol specific.
+ 1 - for multichannel (generic) mode.
+
+Optional properties:
+-------------------
+- clocks : phandle to the input clock.
+- fsl,mu-side-b : Should be set for side B MU.
Examples:
--------
--
2.18.0
next prev parent reply other threads:[~2018-07-18 7:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 7:12 [PATCH v4 0/4] add mailbox support for i.MX7D Oleksij Rempel
2018-07-18 7:12 ` [PATCH v4 1/4] dt-bindings: arm: fsl: add mu binding doc Oleksij Rempel
2018-07-18 7:12 ` Oleksij Rempel [this message]
2018-07-18 9:14 ` [PATCH v4 2/4] dt-bindings: arm: fsl: rework mu doc A.s. Dong
2018-07-18 7:12 ` [PATCH v4 3/4] ARM: dts: imx7s: add i.MX7 messaging unit support Oleksij Rempel
2018-07-18 7:12 ` [PATCH v4 4/4] mailbox: Add support for i.MX7D messaging unit Oleksij Rempel
2018-07-18 7:57 ` Vladimir Zapolskiy
2018-07-18 9:47 ` A.s. Dong
2018-07-21 11:40 ` Oleksij Rempel
2018-07-21 13:06 ` A.s. Dong
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=20180718071251.8857-3-o.rempel@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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 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).