From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 2/4] dt-bindings: mailbox: provide imx-mailbox documentation
Date: Tue, 12 Jun 2018 13:41:42 -0600 [thread overview]
Message-ID: <20180612194142.GA16521@rob-hp-laptop> (raw)
In-Reply-To: <20180601065821.28234-3-o.rempel@pengutronix.de>
On Fri, Jun 01, 2018 at 08:58:19AM +0200, Oleksij Rempel wrote:
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> .../bindings/mailbox/imx-mailbox.txt | 35 +++++++++++++++++++
> 1 file changed, 35 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/mailbox/imx-mailbox.txt
>
> diff --git a/Documentation/devicetree/bindings/mailbox/imx-mailbox.txt b/Documentation/devicetree/bindings/mailbox/imx-mailbox.txt
> new file mode 100644
> index 000000000000..a45604b33039
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/mailbox/imx-mailbox.txt
> @@ -0,0 +1,35 @@
> +i.MX Messaging Unit
> +===================
> +
> +The i.MX Messaging Unit (MU) contains two register sets: "A" and "B". In most cases
> +they are accessible from all Processor Units. On one hand, at least for mailbox functionality,
> +it makes no difference which application or processor is using which set of the MU. On
Please wrap lines correctly (<80).
> +other hand, the register sets for each of the MU parts are not identical.
> +
> +Required properties:
> +- compatible : Shell be one of:
> + "fsl,imx7s-mu-a" and "fsl,imx7s-mu-b" for i.MX7S or i.MX7D
> +- reg : physical base address of the mailbox and length of
Mix of space and tab.
> + memory mapped region.
> +- #mbox-cells: Common mailbox binding property to identify the number
> + of cells required for the mailbox specifier. Should be 1.
> +- interrupts : interrupt number. The interrupt specifier format
> + depends on the interrupt controller parent.
Just need to say how many interrupts and what they are if more than 1.
> +- clocks : phandle to the input clock.
> +
> +Example:
> + mu0a: mu at 30aa0000 {
mailbox at ...
> + compatible = "fsl,imx7s-mu-a";
> + reg = <0x30aa0000 0x28>;
> + interrupts = <GIC_SPI 88 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&clks IMX7D_MU_ROOT_CLK>;
> + #mbox-cells = <1>;
> + };
> +
> + mu0b: mu at 30ab0000 {
mailbox at ...
> + compatible = "fsl,imx7s-mu-b";
> + reg = <0x30ab0000 0x28>;
> + interrupts = <GIC_SPI 97 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&clks IMX7D_MU_ROOT_CLK>;
> + #mbox-cells = <1>;
> + };
> --
> 2.17.1
>
next prev parent reply other threads:[~2018-06-12 19:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 6:58 [PATCH v1 0/4] add mailbox support for i.MX7D Oleksij Rempel
2018-06-01 6:58 ` [PATCH v1 1/4] clk: imx7d: add IMX7D_MU_ROOT_CLK Oleksij Rempel
2018-06-13 10:38 ` Dong Aisheng
2018-06-01 6:58 ` [PATCH v1 2/4] dt-bindings: mailbox: provide imx-mailbox documentation Oleksij Rempel
2018-06-12 19:41 ` Rob Herring [this message]
2018-06-13 11:59 ` Oleksij Rempel
2018-06-13 11:05 ` Dong Aisheng
2018-06-13 11:58 ` Oleksij Rempel
2018-06-01 6:58 ` [PATCH v1 3/4] ARM: dts: imx7s: add i.MX7 messaging unit support Oleksij Rempel
2018-06-01 6:58 ` [PATCH v1 4/4] mailbox: Add support for i.MX7D messaging unit Oleksij Rempel
2018-06-13 12:21 ` Dong Aisheng
2018-06-13 12:24 ` Dong Aisheng
2018-06-15 6:23 ` Oleksij Rempel
2018-06-13 12:48 ` Sascha Hauer
2018-06-14 8:23 ` Dong Aisheng
2018-06-14 10:24 ` Oleksij Rempel
2018-06-01 8:34 ` [PATCH v1 0/4] add mailbox support for i.MX7D Robert Schwebel
2018-06-13 9:36 ` 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=20180612194142.GA16521@rob-hp-laptop \
--to=robh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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