From: Dong Aisheng <aisheng.dong@nxp.com> To: linux-arm-kernel@lists.infradead.org Cc: Dong Aisheng <aisheng.dong@nxp.com>, Mark Rutland <mark.rutland@arm.com>, dongas86@gmail.com, devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>, linux-imx@nxp.com, kernel@pengutronix.de, fabio.estevam@nxp.com, shawnguo@kernel.org Subject: [PATCH V2 2/4] dt-bindings: arm: fsl: add mu binding doc Date: Sun, 17 Jun 2018 20:49:47 +0800 [thread overview] Message-ID: <1529239789-26849-3-git-send-email-aisheng.dong@nxp.com> (raw) In-Reply-To: <1529239789-26849-1-git-send-email-aisheng.dong@nxp.com> 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. Cc: Shawn Guo <shawnguo@kernel.org> Cc: Sascha Hauer <kernel@pengutronix.de> Cc: Fabio Estevam <fabio.estevam@nxp.com> Cc: Rob Herring <robh+dt@kernel.org> Cc: Mark Rutland <mark.rutland@arm.com> Cc: devicetree@vger.kernel.org Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com> --- v1->v2: * typo fixes * remove status property * remove imx6&7 compatible string which may be added later for the generic mailbox binding Note: Because MU used by SCU is not implemented as a mailbox driver, Instead, they're provided in library calls to gain higher performance. Futhermore, SCU MU has only one channel. But the binding doc claims (Change to allow 0?) So we did not follow the mailbox binding. For the generic mailbox driver binding way, it may be added later. --- .../devicetree/bindings/arm/freescale/fsl,mu.txt | 32 ++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,mu.txt diff --git a/Documentation/devicetree/bindings/arm/freescale/fsl,mu.txt b/Documentation/devicetree/bindings/arm/freescale/fsl,mu.txt new file mode 100644 index 0000000..c37aa1d --- /dev/null +++ b/Documentation/devicetree/bindings/arm/freescale/fsl,mu.txt @@ -0,0 +1,32 @@ +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. +- reg : Should contain the registers location and length +- interrupts : Interrupt number. The interrupt specifier format depends + on the interrupt controller parent. + +Examples: +-------- +lsio_mu0: mu@5d1b0000 { + compatible = "fsl,imx8qxp-mu"; + reg = <0x0 0x5d1b0000 0x0 0x10000>; + interrupts = <GIC_SPI 176 IRQ_TYPE_LEVEL_HIGH>; +}; -- 2.7.4
WARNING: multiple messages have this Message-ID (diff)
From: aisheng.dong@nxp.com (Dong Aisheng) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH V2 2/4] dt-bindings: arm: fsl: add mu binding doc Date: Sun, 17 Jun 2018 20:49:47 +0800 [thread overview] Message-ID: <1529239789-26849-3-git-send-email-aisheng.dong@nxp.com> (raw) In-Reply-To: <1529239789-26849-1-git-send-email-aisheng.dong@nxp.com> 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. Cc: Shawn Guo <shawnguo@kernel.org> Cc: Sascha Hauer <kernel@pengutronix.de> Cc: Fabio Estevam <fabio.estevam@nxp.com> Cc: Rob Herring <robh+dt@kernel.org> Cc: Mark Rutland <mark.rutland@arm.com> Cc: devicetree at vger.kernel.org Signed-off-by: Dong Aisheng <aisheng.dong@nxp.com> --- v1->v2: * typo fixes * remove status property * remove imx6&7 compatible string which may be added later for the generic mailbox binding Note: Because MU used by SCU is not implemented as a mailbox driver, Instead, they're provided in library calls to gain higher performance. Futhermore, SCU MU has only one channel. But the binding doc claims (Change to allow 0?) So we did not follow the mailbox binding. For the generic mailbox driver binding way, it may be added later. --- .../devicetree/bindings/arm/freescale/fsl,mu.txt | 32 ++++++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,mu.txt diff --git a/Documentation/devicetree/bindings/arm/freescale/fsl,mu.txt b/Documentation/devicetree/bindings/arm/freescale/fsl,mu.txt new file mode 100644 index 0000000..c37aa1d --- /dev/null +++ b/Documentation/devicetree/bindings/arm/freescale/fsl,mu.txt @@ -0,0 +1,32 @@ +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. +- reg : Should contain the registers location and length +- interrupts : Interrupt number. The interrupt specifier format depends + on the interrupt controller parent. + +Examples: +-------- +lsio_mu0: mu at 5d1b0000 { + compatible = "fsl,imx8qxp-mu"; + reg = <0x0 0x5d1b0000 0x0 0x10000>; + interrupts = <GIC_SPI 176 IRQ_TYPE_LEVEL_HIGH>; +}; -- 2.7.4
next prev parent reply other threads:[~2018-06-17 12:49 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-06-17 12:49 [PATCH V2 0/4] soc: imx: add scu firmware api support Dong Aisheng 2018-06-17 12:49 ` [PATCH V2 1/4] soc: imx: add mu library functions support Dong Aisheng 2018-06-17 12:49 ` Dong Aisheng [this message] 2018-06-17 12:49 ` [PATCH V2 2/4] dt-bindings: arm: fsl: add mu binding doc Dong Aisheng 2018-06-20 19:43 ` Rob Herring 2018-06-20 19:43 ` Rob Herring 2018-06-21 7:46 ` Sascha Hauer 2018-06-21 7:46 ` Sascha Hauer 2018-06-21 17:11 ` A.s. Dong 2018-06-21 17:11 ` A.s. Dong 2018-06-21 18:08 ` Oleksij Rempel 2018-06-21 18:08 ` Oleksij Rempel 2018-06-22 3:31 ` A.s. Dong 2018-06-22 3:31 ` A.s. Dong 2018-06-22 4:59 ` Oleksij Rempel 2018-06-22 4:59 ` Oleksij Rempel 2018-06-22 5:59 ` A.s. Dong 2018-06-22 5:59 ` A.s. Dong 2018-06-22 6:48 ` Oleksij Rempel 2018-06-22 6:48 ` Oleksij Rempel 2018-06-22 8:16 ` A.s. Dong 2018-06-22 8:16 ` A.s. Dong 2018-06-22 5:49 ` Sascha Hauer 2018-06-22 5:49 ` Sascha Hauer 2018-06-22 6:04 ` A.s. Dong 2018-06-22 6:04 ` A.s. Dong 2018-06-17 12:49 ` [PATCH V2 3/4] dt-bindings: arm: fsl: add scu " Dong Aisheng 2018-06-17 12:49 ` Dong Aisheng 2018-06-20 19:44 ` Rob Herring 2018-06-20 19:44 ` Rob Herring 2018-06-21 3:38 ` A.s. Dong 2018-06-21 3:38 ` A.s. Dong 2018-06-21 7:37 ` Sascha Hauer 2018-06-21 7:37 ` Sascha Hauer 2018-06-21 12:05 ` A.s. Dong 2018-06-21 12:05 ` A.s. Dong [not found] ` <1529239789-26849-5-git-send-email-aisheng.dong@nxp.com> 2018-06-18 8:58 ` [PATCH V2 4/4] soc: imx: add SC firmware IPC and APIs Leonard Crestez
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=1529239789-26849-3-git-send-email-aisheng.dong@nxp.com \ --to=aisheng.dong@nxp.com \ --cc=devicetree@vger.kernel.org \ --cc=dongas86@gmail.com \ --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: linkBe 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.