Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3696014imj; Tue, 19 Feb 2019 07:56:26 -0800 (PST) X-Google-Smtp-Source: AHgI3Ia0Gz3fgteU7zGq5/HpUSc8IxB5zDoHyXylKgU4+d3Yxf58gAjYbbsW04JpD+pf20ZF7Lo1 X-Received: by 2002:a63:2c8c:: with SMTP id s134mr24818506pgs.269.1550591786087; Tue, 19 Feb 2019 07:56:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550591786; cv=none; d=google.com; s=arc-20160816; b=PxXMfbEyYXgnCcp4D+rxPbM+ku0aaaNN8prTGTgA6UF9QwDf3oJ1FK2qOn5pi39wtp 3lVQfY7Sa/Lt9lcoT7l5cQgSZC9W6i5GdsKRu+HiUSMpuBkif7aUZ3UYakgFNquPw/0L C5KuReWmsrcQ+1NebYnn288tHzpBi/yqGia65lsRngbWXiV0E4DwE9BE6lxjm6dZ2KM8 BVIhsy2DWeNxUcsoygaXlm8udRGiEzY3gOx9nNy+x78BUF/MOBUTKJZsGuPiWTB+FkcY 2LpmUTfxB/lQm7Lioj+n0cp5PmPx/Zt+BoMBSft7HdJmlQywkAE5BwF8Wa1iVrtV1ei7 0sgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=dCxqk8R5FltkNLqhj+4knXlOYNjjOaUJAtD7ZCtW4sg=; b=AFucKUSPQmC5j16GCF6Dxm1uDrMV7XVAzzM9ckqOrbL/KU8TxCs9oLZjUjHHUX4XCX HBNlncrv+8ibUXSCHAavjuh8gWY6KU3anIY92ZDhddm8WqLV25t2mOQZ3gAsa3Pytt1e 5jRVHQ/3rojfMGiNgsKG6CBbAckONGquZHccLxD+OfCrXcGTzdLgcB7NIfGFSz7y7P9z A+nKr11Rv5W3Ylg0pEjZGqR4Brw6zPhLeIk8uXg8rT2vaRPW0g0Go6iOlYz6GPV1uRAj Bazq3Veyd52vJYK+yagEjOWLg4M4tEsslteU+Ye1NzFiDsjjC/FhA64pSNtEYn1pV7WZ LXkQ== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i35si14853285plg.396.2019.02.19.07.56.10; Tue, 19 Feb 2019 07:56:26 -0800 (PST) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727982AbfBSPzW (ORCPT + 99 others); Tue, 19 Feb 2019 10:55:22 -0500 Received: from relmlor2.renesas.com ([210.160.252.172]:56594 "EHLO relmlie6.idc.renesas.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725820AbfBSPzW (ORCPT ); Tue, 19 Feb 2019 10:55:22 -0500 X-IronPort-AV: E=Sophos;i="5.58,388,1544454000"; d="scan'208";a="8079557" Received: from unknown (HELO relmlir6.idc.renesas.com) ([10.200.68.152]) by relmlie6.idc.renesas.com with ESMTP; 20 Feb 2019 00:55:20 +0900 Received: from vbox.ree.adwin.renesas.com (unknown [10.226.37.67]) by relmlir6.idc.renesas.com (Postfix) with ESMTP id A92D2409EDE3; Wed, 20 Feb 2019 00:55:17 +0900 (JST) From: Phil Edworthy To: Rob Herring , Mark Rutland , Marc Zyngier , Thomas Gleixner , Jason Cooper Cc: Phil Edworthy , Geert Uytterhoeven , devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v4 0/2] irqchip: Add support for Renesas RZ/N1 GPIO interrupt multiplexer Date: Tue, 19 Feb 2019 15:55:09 +0000 Message-Id: <20190219155511.28507-1-phil.edworthy@renesas.com> X-Mailer: git-send-email 2.17.1 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On RZ/N1 devices, there are lots of GPIO interrupts that are multiplexed before getting to the GIC interrupt controller. Other than the multiplexing, there is no other logic applied to the signals. The multiplexing cannot be handled dynamically because there is another CPU that runs firmware. It's likely that the firmware will use some of these GPIO interrupts and so we don't want them to move around. Signed-off-by: Phil Edworthy --- v4: - Fix DT binding nits v3: - Use 'interrupt-map' DT property to map the interrupts, this is very similar to PCIe MSI. The only difference is that we need to get hold of the interrupt specifier for the interupts coming into the irqmux. I had completely messed up the use of 'interrupt-map' in v2... oops. - Do not use a chained interrupt controller. v2: - Split DT bindings into separate patch. - Use interrupt-map to allow the GPIO controller info to be specified as part of the irq. - Don't show status in binding examples. - Don't show the soc/board split in binding doc. - Renamed struct and funcs from 'girq' to a more comprehenisble 'irqmux'. Phil Edworthy (2): dt-bindings/interrupt-controller: rzn1: Add RZ/N1 gpio irq mux binding irqchip: Add support for Renesas RZ/N1 GPIO interrupt multiplexer .../interrupt-controller/renesas,rzn1-mux.txt | 73 +++++++ drivers/irqchip/Kconfig | 9 + drivers/irqchip/Makefile | 1 + drivers/irqchip/rzn1-irq-mux.c | 205 ++++++++++++++++++ 4 files changed, 288 insertions(+) create mode 100644 Documentation/devicetree/bindings/interrupt-controller/renesas,rzn1-mux.txt create mode 100644 drivers/irqchip/rzn1-irq-mux.c -- 2.17.1