Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp316067yba; Sat, 20 Apr 2019 03:14:23 -0700 (PDT) X-Google-Smtp-Source: APXvYqwojXpKJBp8dfdNFk/8FBH6fyrkHDhTR1hRPI8OYOxOFC77+q/msgsvCp2gp3xyqjsgzx1d X-Received: by 2002:a65:6496:: with SMTP id e22mr8597144pgv.249.1555755263548; Sat, 20 Apr 2019 03:14:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1555755263; cv=none; d=google.com; s=arc-20160816; b=lej6OPU+sOjaKuiX4iERI7/DV/nVZ2IRBCTxzKkOvhcuzK2DBii59W0dEGEoAqeUEv uWG3k4uoWHa32fhOZy6arz+F/HTmDfsSYn0d5wq3/OVx3i/Chgndf3W90DlZfs/NDSU6 rumD+T+qeqqgj6UxrqHjv6pQqtMH+ihsxBfDiHjrzbQz3+EG+8blzVhn6pPGvHUVsJ/a GwtY85Qcgz9whsv+dk6zhnuJaKqzdDTjAuBBjUOR9FJfZbj9qLLp8enTgDY1IXIg82nl Upq+BT7gRczPrzy0OVWEvf+UpD5rZh1QChyDzQelPXLKmPFBshgW8a52+6mY2koiq4mw MUbA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=vk6OcKSyHszZnq8cNh71+s3zN0mtQCYGJIqnq171Kxc=; b=KYIP2BELPBhpI6bFzLk84iKmFV9YbLA45nEuT2plS8r7kfT+y2zzGYxYebz0fGr5e3 wuAaXtUTi2xYQaSeVoACiaESEYwFWaPHoIgV/ZpsptDuAalgwNN09s9Vfuh2WmXbs3uM ZT5qYn1ZZKkPlwSME5mG2mkZIyrrrRZvi/vzo/F8eb3LQm+6z3Ty7V7z1MgRDQqxnKVX APo4vMxh8vkXekXMKBXIBDOTs8TsH+IzNEPh4cJU7Cdg2c8ZeztW8argoiq0jjo5UAE+ WK8hnuXcxHePgdi1kRgIw4srUy8svHBlLL1HHOA0t1yiWKZd6Ah+HV0iBExa5Rdewv4B GlNA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b="X0fGT/5s"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j190si7215030pgd.423.2019.04.20.03.13.33; Sat, 20 Apr 2019 03:14:23 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b="X0fGT/5s"; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728190AbfDTKL2 (ORCPT + 99 others); Sat, 20 Apr 2019 06:11:28 -0400 Received: from fllv0015.ext.ti.com ([198.47.19.141]:45830 "EHLO fllv0015.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727218AbfDTKL1 (ORCPT ); Sat, 20 Apr 2019 06:11:27 -0400 Received: from lelv0266.itg.ti.com ([10.180.67.225]) by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id x3KAAx4n007973; Sat, 20 Apr 2019 05:10:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1555755059; bh=vk6OcKSyHszZnq8cNh71+s3zN0mtQCYGJIqnq171Kxc=; h=From:To:CC:Subject:Date:In-Reply-To:References; b=X0fGT/5sTFQKa93vWc2NGoMJsaRa4LdwMFQqIyL7IsCbcv4Km4rbGjTfESZreHirl 4mjkrMUkVXf0vdFxN1dqV9owi2KmYCk4egxvsVB2Quxuxxmcj2P6uZcsAFYX7U2cEF 2YDzOxnYmmpLswQKq4um/CiUjOhn62vLPNIfe2Mo= Received: from DFLE103.ent.ti.com (dfle103.ent.ti.com [10.64.6.24]) by lelv0266.itg.ti.com (8.15.2/8.15.2) with ESMTPS id x3KAAxMl042460 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Sat, 20 Apr 2019 05:10:59 -0500 Received: from DFLE105.ent.ti.com (10.64.6.26) by DFLE103.ent.ti.com (10.64.6.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Sat, 20 Apr 2019 05:10:58 -0500 Received: from lelv0326.itg.ti.com (10.180.67.84) by DFLE105.ent.ti.com (10.64.6.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5 via Frontend Transport; Sat, 20 Apr 2019 05:10:58 -0500 Received: from uda0131933.india.ti.com (ileax41-snat.itg.ti.com [10.172.224.153]) by lelv0326.itg.ti.com (8.15.2/8.15.2) with ESMTP id x3KAAHZx070234; Sat, 20 Apr 2019 05:10:54 -0500 From: Lokesh Vutla To: Marc Zyngier , Santosh Shilimkar , Rob Herring , Nishanth Menon , , CC: Linux ARM Mailing List , , Tero Kristo , Sekhar Nori , Tony Lindgren , , Peter Ujfalusi , Grygorii Strashko , Lokesh Vutla , Device Tree Mailing List Subject: [PATCH v7 08/14] dt-bindings: irqchip: Introduce TISCI Interrupt router bindings Date: Sat, 20 Apr 2019 15:39:44 +0530 Message-ID: <20190420100950.7997-9-lokeshvutla@ti.com> X-Mailer: git-send-email 2.21.0 In-Reply-To: <20190420100950.7997-1-lokeshvutla@ti.com> References: <20190420100950.7997-1-lokeshvutla@ti.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Add the DT binding documentation for Interrupt router driver. Signed-off-by: Lokesh Vutla --- Changes since v6: - None. New firmware is bound to release this month end. When released, Ill repost with interrupt cells as 2. .../interrupt-controller/ti,sci-intr.txt | 84 +++++++++++++++++++ MAINTAINERS | 1 + 2 files changed, 85 insertions(+) create mode 100644 Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.txt diff --git a/Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.txt b/Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.txt new file mode 100644 index 000000000000..952a74609367 --- /dev/null +++ b/Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.txt @@ -0,0 +1,84 @@ +Texas Instruments K3 Interrupt Router +===================================== + +The Interrupt Router (INTR) module provides a mechanism to mux M +interrupt inputs to N interrupt outputs, where all M inputs are selectable +to be driven per N output. An Interrupt Router can either handle edge triggered +or level triggered interrupts and that is fixed in hardware. + + Interrupt Router + +----------------------+ + | Inputs Outputs | + +-------+ | +------+ +-----+ | + | GPIO |----------->| | irq0 | | 0 | | Host IRQ + +-------+ | +------+ +-----+ | controller + | . . | +-------+ + +-------+ | . . |----->| IRQ | + | INTA |----------->| . . | +-------+ + +-------+ | . +-----+ | + | +------+ | N | | + | | irqM | +-----+ | + | +------+ | + | | + +----------------------+ + +There is one register per output (MUXCNTL_N) that controls the selection. +Configuration of these MUXCNTL_N registers is done by a system controller +(like the Device Memory and Security Controller on K3 AM654 SoC). System +controller will keep track of the used and unused registers within the Router. +Driver should request the system controller to get the range of GIC IRQs +assigned to the requesting hosts. It is the drivers responsibility to keep +track of Host IRQs. + +Communication between the host processor running an OS and the system +controller happens through a protocol called TI System Control Interface +(TISCI protocol). For more details refer: +Documentation/devicetree/bindings/arm/keystone/ti,sci.txt + +TISCI Interrupt Router Node: +---------------------------- +Required Properties: +- compatible: Must be "ti,sci-intr". +- ti,intr-trigger-type: Should be one of the following: + 1: If intr supports edge triggered interrupts. + 4: If intr supports level triggered interrupts. +- interrupt-controller: Identifies the node as an interrupt controller +- #interrupt-cells: Specifies the number of cells needed to encode an + interrupt source. The value should be 3. + First cell should contain the TISCI device ID of source + Second cell should contain the interrupt source offset + within the device. + Third cell should be 1 if the irq is coming from the + interrupt aggregator else 0. +- ti,sci: Phandle to TI-SCI compatible System controller node. +- ti,sci-dst-id: TISCI device ID of the destination IRQ controller. +- ti,sci-rm-range-girq: Array of TISCI subtype ids representing the host irqs + assigned to this interrupt router. Each subtype id + corresponds to a range of host irqs. + +For more details on TISCI IRQ resource management refer: +http://downloads.ti.com/tisci/esd/latest/2_tisci_msgs/rm/rm_irq.html + +Example: +-------- +The following example demonstrates both interrupt router node and the consumer +node(main gpio) on the AM654 SoC: + +main_intr: interrupt-controller0 { + compatible = "ti,sci-intr"; + ti,intr-trigger-type = <1>; + interrupt-controller; + interrupt-parent = <&gic500>; + #interrupt-cells = <3>; + ti,sci = <&dmsc>; + ti,sci-dst-id = <56>; + ti,sci-rm-range-girq = <0x1>; +}; + +main_gpio0: gpio@600000 { + ... + interrupt-parent = <&main_intr>; + interrupts = <57 256 0>, <57 257 0>, <57 258 0>, + <57 259 0>, <57 260 0>, <57 261 0>; + ... +}; diff --git a/MAINTAINERS b/MAINTAINERS index 3671fdea5010..b40762656a6d 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -15349,6 +15349,7 @@ F: Documentation/devicetree/bindings/reset/ti,sci-reset.txt F: Documentation/devicetree/bindings/clock/ti,sci-clk.txt F: drivers/clk/keystone/sci-clk.c F: drivers/reset/reset-ti-sci.c +F: Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.txt Texas Instruments ASoC drivers M: Peter Ujfalusi -- 2.21.0