From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oleksij Rempel Subject: [PATCH v1 0/4] add mailbox support for i.MX7D Date: Fri, 1 Jun 2018 08:58:17 +0200 Message-ID: <20180601065821.28234-1-o.rempel@pengutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Shawn Guo , Fabio Estevam , Rob Herring , Mark Rutland Cc: Oleksij Rempel , linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kernel@pengutronix.de, devicetree@vger.kernel.org List-Id: devicetree@vger.kernel.org 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 | 289 ++++++++++++++++++ 6 files changed, 351 insertions(+) create mode 100644 Documentation/devicetree/bindings/mailbox/imx-mailbox.txt create mode 100644 drivers/mailbox/imx-mailbox.c -- 2.17.1