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>,
Vladimir Zapolskiy <vladimir_zapolskiy@mentor.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 v6 3/5] dt-bindings: mailbox: imx-mu: add generic MU channel support
Date: Sun, 22 Jul 2018 08:39:21 +0200 [thread overview]
Message-ID: <20180722063923.30222-4-o.rempel@pengutronix.de> (raw)
In-Reply-To: <20180722063923.30222-1-o.rempel@pengutronix.de>
Each MU has four pairs of rx/tx data register with four rx/tx interrupts
which can also be used as a separate channel.
Reviewed-by: Dong Aisheng <aisheng.dong@nxp.com>
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
---
Documentation/devicetree/bindings/mailbox/fsl,mu.txt | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mailbox/fsl,mu.txt b/Documentation/devicetree/bindings/mailbox/fsl,mu.txt
index 90e4905dfc69..113d6ab931ef 100644
--- a/Documentation/devicetree/bindings/mailbox/fsl,mu.txt
+++ b/Documentation/devicetree/bindings/mailbox/fsl,mu.txt
@@ -22,7 +22,14 @@ Required properties:
- 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-22 6:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-22 6:39 [PATCH v6 0/5] add mailbox support for i.MX7D Oleksij Rempel
2018-07-22 6:39 ` [PATCH v6 1/5] dt-bindings: mailbox: allow mbox-cells to be equal to 0 Oleksij Rempel
2018-07-22 6:39 ` [PATCH v6 2/5] dt-bindings: arm: fsl: add mu binding doc Oleksij Rempel
2018-07-22 6:39 ` Oleksij Rempel [this message]
2018-07-24 23:19 ` [PATCH v6 3/5] dt-bindings: mailbox: imx-mu: add generic MU channel support Rob Herring
2018-07-22 6:39 ` [PATCH v6 4/5] ARM: dts: imx7s: add i.MX7 messaging unit support Oleksij Rempel
2018-07-23 16:57 ` Lucas Stach
2018-07-24 2:04 ` A.s. Dong
2018-07-22 6:39 ` [PATCH v6 5/5] mailbox: Add support for i.MX7D messaging unit Oleksij Rempel
2018-07-23 17:19 ` Lucas Stach
2018-07-23 19:11 ` Oleksij Rempel
2018-07-24 2:09 ` A.s. Dong
2018-07-24 5:14 ` Oleksij Rempel
2018-07-24 9:06 ` Lucas Stach
2018-07-23 23:31 ` Vladimir Zapolskiy
2018-07-24 2:13 ` A.s. Dong
2018-07-24 4:38 ` Oleksij Rempel
2018-07-22 10:44 ` [PATCH v6 0/5] add mailbox support for i.MX7D A.s. Dong
2018-07-23 15:33 ` Jassi Brar
2018-07-24 2:18 ` 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=20180722063923.30222-4-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 \
--cc=vladimir_zapolskiy@mentor.com \
/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).