From mboxrd@z Thu Jan 1 00:00:00 1970 From: o.rempel@pengutronix.de (Oleksij Rempel) Date: Wed, 13 Jun 2018 13:59:30 +0200 Subject: [PATCH v1 2/4] dt-bindings: mailbox: provide imx-mailbox documentation In-Reply-To: <20180612194142.GA16521@rob-hp-laptop> References: <20180601065821.28234-1-o.rempel@pengutronix.de> <20180601065821.28234-3-o.rempel@pengutronix.de> <20180612194142.GA16521@rob-hp-laptop> Message-ID: <034f77a2-88b5-716b-d9c8-10d73beec9d4@pengutronix.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 12.06.2018 21:41, Rob Herring wrote: > On Fri, Jun 01, 2018 at 08:58:19AM +0200, Oleksij Rempel wrote: >> Signed-off-by: Oleksij Rempel >> --- >> .../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 = ; >> + clocks = <&clks IMX7D_MU_ROOT_CLK>; >> + #mbox-cells = <1>; >> + }; >> + >> + mu0b: mu at 30ab0000 { > > mailbox at ... > >> + compatible = "fsl,imx7s-mu-b"; >> + reg = <0x30ab0000 0x28>; >> + interrupts = ; >> + clocks = <&clks IMX7D_MU_ROOT_CLK>; >> + #mbox-cells = <1>; >> + }; thx. will fix it. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: