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>
Cc: devicetree@vger.kernel.org,
Oleksij Rempel <o.rempel@pengutronix.de>,
dl-linux-imx <linux-imx@nxp.com>,
kernel@pengutronix.de, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] add mailbox support for i.MX7D
Date: Fri, 15 Jun 2018 11:51:03 +0200 [thread overview]
Message-ID: <20180615095107.24610-1-o.rempel@pengutronix.de> (raw)
20180615 changes v2:
- DT: use mailbox@ instead of mu@
- DT: change interrupts description
- clk: use imx_clk_gate4 instead of imx_clk_gate2
- imx-mailbox: remove last_tx_done support
- imx-mailbox: fix module description
This patches are providing support for mailbox (Messaging Unit)
for i.MX7D.
Functionality was tested on PHYTEC phyBOARD-Zeta i.MX7D with
Linux running on all cores: ARM Cortex-A7 and ARM Cortex-M4.
Both parts of i.MX messaging Unit are visible for all CPUs available
on i.MX7D. Communication worked independent of MU side in combination
with CPU. For example MU-A used on ARM Cortex-A7 and MU-B used on ARM Cortex-M4
or other ways around.
The question to NXP developers: are there are limitations or
recommendations about MU vs CPU combination? The i.MX7D documentation
talks about "Processor A" and "Processor B". It is not quite clear what
processor it actually is (A7 or M4).
Oleksij Rempel (4):
clk: imx7d: add IMX7D_MU_ROOT_CLK
dt-bindings: mailbox: provide imx-mailbox documentation
ARM: dts: imx7s: add i.MX7 messaging unit support
mailbox: Add support for i.MX7D messaging unit
.../bindings/mailbox/imx-mailbox.txt | 35 +++
arch/arm/boot/dts/imx7s.dtsi | 18 ++
drivers/clk/imx/clk-imx7d.c | 1 +
drivers/mailbox/Kconfig | 6 +
drivers/mailbox/Makefile | 2 +
drivers/mailbox/imx-mailbox.c | 288 ++++++++++++++++++
6 files changed, 350 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mailbox/imx-mailbox.txt
create mode 100644 drivers/mailbox/imx-mailbox.c
--
2.17.1
next reply other threads:[~2018-06-15 9:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 9:51 Oleksij Rempel [this message]
2018-06-15 9:51 ` [PATCH v2 1/4] clk: imx7d: add IMX7D_MU_ROOT_CLK Oleksij Rempel
2018-07-09 6:22 ` Stephen Boyd
2018-07-09 6:28 ` Oleksij Rempel
2018-07-09 8:18 ` A.s. Dong
2018-07-09 12:47 ` Fabio Estevam
2018-07-09 16:57 ` Stephen Boyd
2018-06-15 9:51 ` [PATCH v2 2/4] dt-bindings: mailbox: provide imx-mailbox documentation Oleksij Rempel
2018-06-18 8:53 ` Leonard Crestez
2018-06-18 11:51 ` Oleksij Rempel
2018-06-15 9:51 ` [PATCH v2 3/4] ARM: dts: imx7s: add i.MX7 messaging unit support Oleksij Rempel
2018-06-15 9:51 ` [PATCH v2 4/4] mailbox: Add support for i.MX7D messaging unit Oleksij Rempel
2018-06-26 10:09 ` A.s. Dong
2018-06-26 10:56 ` Oleksij Rempel
2018-06-26 12:07 ` A.s. Dong
2018-07-02 7:35 ` Oleksij Rempel
2018-06-26 13:23 ` Sascha Hauer
2018-06-27 3:18 ` A.s. Dong
2018-07-12 11:28 ` A.s. Dong
2018-07-14 7:02 ` Oleksij Rempel
2018-07-14 8:49 ` A.s. Dong
2018-07-14 9:41 ` Oleksij Rempel
2018-07-14 11:41 ` 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=20180615095107.24610-1-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-clk@vger.kernel.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: 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).