From nobody Mon May 6 02:21:13 2024 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 61719C433F5 for ; Thu, 29 Sep 2022 16:28:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235971AbiI2Q1o (ORCPT ); Thu, 29 Sep 2022 12:27:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57400 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235310AbiI2Q1I (ORCPT ); Thu, 29 Sep 2022 12:27:08 -0400 Received: from galois.linutronix.de (Galois.linutronix.de [IPv6:2a0a:51c0:0:12e:550::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7E58A13A061 for ; Thu, 29 Sep 2022 09:26:23 -0700 (PDT) Date: Thu, 29 Sep 2022 16:26:18 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1664468781; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4LAsNz8jL1zZ2kJLVm/0pZMkI5re6qTl5qguOofolbs=; b=ABbQYnIrpZbGag80rue9iIvi5E/ef3BT31ZNt6nHr9+bcix7vU38LXYHecucN5xM8K6iNd uEa8gvfvxP+nmMkXu44FHY4Og/mMOJjNeZb6ZLDOf+jzkq0VoOXHLalbPY3OULq6NavvDC ySImlgxhrJ3sy01Ki+WAW2Zbf5/kALqKNGN6kMvQK6DmVwLAZUS9fJkM91OXbcCunORcXZ m8jSc+xnCFK8bkB8wGd6d5U0cAIog6DgP88WVB0Su/iyzTWijEV9JBnDU3/u9SQ3Jqr6io pCERlnnioUkoAdhM5m/WdPdtjRSBrlMjOKFwkRJol1VvrVAEavnV4MYZgMQGkw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1664468781; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4LAsNz8jL1zZ2kJLVm/0pZMkI5re6qTl5qguOofolbs=; b=6xj+Bub5XUSlAvYD4miq2xRLcrfDXwnAsw9Z2JHGL4m+HYODVymLR6dxCePf/qcXQFxGtJ Jx8mtZFni+xcX1Dg== From: "irqchip-bot for Frank Li" Sender: tip-bot2@linutronix.de Reply-to: linux-kernel@vger.kernel.org To: linux-kernel@vger.kernel.org Subject: [irqchip: irq/irqchip-next] dt-bindings: irqchip: Describe the IMX MU block as a MSI controller Cc: Rob Herring , Frank Li , Marc Zyngier , tglx@linutronix.de In-Reply-To: <20220922161246.20586-5-Frank.Li@nxp.com> References: <20220922161246.20586-5-Frank.Li@nxp.com> MIME-Version: 1.0 Message-ID: <166446877886.401.15287882873684191652.tip-bot2@tip-bot2> Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The following commit has been merged into the irq/irqchip-next branch of ir= qchip: Commit-ID: 7c025238b47a55c81c61dfe85a200ab82e6a6ece Gitweb: https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-plat= forms/7c025238b47a55c81c61dfe85a200ab82e6a6ece Author: Frank Li AuthorDate: Thu, 22 Sep 2022 11:12:44 -05:00 Committer: Marc Zyngier CommitterDate: Thu, 29 Sep 2022 17:19:36 +01:00 dt-bindings: irqchip: Describe the IMX MU block as a MSI controller I.MX MU supports generating IRQs by writing to a register. Describe its use as a MSI controller so that other blocks (such as a PCI EP) can use it directly. Reviewed-by: Rob Herring Signed-off-by: Frank Li [maz: commit message] Signed-off-by: Marc Zyngier Link: https://lore.kernel.org/r/20220922161246.20586-5-Frank.Li@nxp.com --- Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.yaml | = 99 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++- 1 file changed, 99 insertions(+) create mode 100644 Documentation/devicetree/bindings/interrupt-controller/= fsl,mu-msi.yaml diff --git a/Documentation/devicetree/bindings/interrupt-controller/fsl,mu-= msi.yaml b/Documentation/devicetree/bindings/interrupt-controller/fsl,mu-ms= i.yaml new file mode 100644 index 0000000..799ae5c --- /dev/null +++ b/Documentation/devicetree/bindings/interrupt-controller/fsl,mu-msi.yaml @@ -0,0 +1,99 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/interrupt-controller/fsl,mu-msi.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: Freescale/NXP i.MX Messaging Unit (MU) work as msi controller + +maintainers: + - Frank Li + +description: | + 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 (A side) to signal the other processor (B side) 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-side, Processor B-side). + + MU can work as msi interrupt controller to do doorbell + +allOf: + - $ref: /schemas/interrupt-controller/msi-controller.yaml# + +properties: + compatible: + enum: + - fsl,imx6sx-mu-msi + - fsl,imx7ulp-mu-msi + - fsl,imx8ulp-mu-msi + - fsl,imx8ulp-mu-msi-s4 + + reg: + items: + - description: a side register base address + - description: b side register base address + + reg-names: + items: + - const: processor-a-side + - const: processor-b-side + + interrupts: + description: a side interrupt number. + maxItems: 1 + + clocks: + maxItems: 1 + + power-domains: + items: + - description: a side power domain + - description: b side power domain + + power-domain-names: + items: + - const: processor-a-side + - const: processor-b-side + + interrupt-controller: true + + msi-controller: true + + "#msi-cells": + const: 0 + +required: + - compatible + - reg + - interrupts + - interrupt-controller + - msi-controller + - "#msi-cells" + +additionalProperties: false + +examples: + - | + #include + #include + + msi-controller@5d270000 { + compatible =3D "fsl,imx6sx-mu-msi"; + msi-controller; + #msi-cells =3D <0>; + interrupt-controller; + reg =3D <0x5d270000 0x10000>, /* A side */ + <0x5d300000 0x10000>; /* B side */ + reg-names =3D "processor-a-side", "processor-b-side"; + interrupts =3D ; + power-domains =3D <&pd IMX_SC_R_MU_12A>, + <&pd IMX_SC_R_MU_12B>; + power-domain-names =3D "processor-a-side", "processor-b-side"; + };