From: robh@kernel.org (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 2/4] dt-bindings: arm: fsl: add mu binding doc
Date: Wed, 20 Jun 2018 13:43:10 -0600 [thread overview]
Message-ID: <20180620194310.GA28983@rob-hp-laptop> (raw)
In-Reply-To: <1529239789-26849-3-git-send-email-aisheng.dong@nxp.com>
On Sun, Jun 17, 2018 at 08:49:47PM +0800, Dong Aisheng wrote:
> 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.
Using a binding doesn't mean you have to use an OS's subsystem.
What needs higher performance? What's the performance difference? Why
can't the mailbox framework be improved?
> 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.
The h/w isn't changing later, so no.
> ---
> .../devicetree/bindings/arm/freescale/fsl,mu.txt | 32 ++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/freescale/fsl,mu.txt
next prev parent reply other threads:[~2018-06-20 19:43 UTC|newest]
Thread overview: 20+ 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 ` [PATCH V2 2/4] dt-bindings: arm: fsl: add mu binding doc Dong Aisheng
2018-06-20 19:43 ` Rob Herring [this message]
2018-06-21 7:46 ` Sascha Hauer
2018-06-21 17:11 ` A.s. Dong
2018-06-21 18:08 ` Oleksij Rempel
2018-06-22 3:31 ` A.s. Dong
2018-06-22 4:59 ` Oleksij Rempel
2018-06-22 5:59 ` A.s. Dong
2018-06-22 6:48 ` Oleksij Rempel
2018-06-22 8:16 ` A.s. Dong
2018-06-22 5:49 ` Sascha Hauer
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-20 19:44 ` Rob Herring
2018-06-21 3:38 ` A.s. Dong
2018-06-21 7:37 ` Sascha Hauer
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=20180620194310.GA28983@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