Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp2441625pxk; Mon, 14 Sep 2020 13:30:33 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzxVeGEEsG8Irqv0zwmUBTwA7JAxNOcyNYzb1O1h7mcfTwKeeEUBIGCpCIzr2vZuaNpoyk8 X-Received: by 2002:a17:906:1115:: with SMTP id h21mr16932398eja.273.1600115433602; Mon, 14 Sep 2020 13:30:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600115433; cv=none; d=google.com; s=arc-20160816; b=gDURwmLgcKZEv+kP3D8yj/AOOlr30/ujGBzRVm+1dd0zmOv4APxOuMIAdAls3aERqx QYnz/MdkWMUnnPY8sz4TQsrDDI8tjBfY+ZQ6l3fKGWUU/FjtI36E5/I4p7XKnMHMuyHC r4stZ8c649/tnIs+5RGC3TfgzS6p5WzlxgNHxkDYnQ2MAi6qxhcbrvDJNRhm50YkoRaH ZvRoCMJx/TcwGN61LE+VCMVFIWzJedwF8D2d4me7eOWgqcDRPO7wBZjHIzdJUiVm4VC2 IvgUGoyZ80CsKMBBJVUZGqan1bcJOaZo3xw1fRgbM7b+U7YNhi9dBDigBVZnffq98Jw3 +w3w== 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 :message-id:date:subject:cc:to:from:dkim-signature; bh=QFsgSw1+LH8tFMbI6flA4kr5+81BTDk8dyeIbjo4qWM=; b=rj4rXiJwJ39/H5klgChUTrRFlAXnorIRgUxWpySxNJWG6cx/5G4nx0TJP7/diShYhs 1Himxg0KnLiIeREXWMymKH0iL2h8UAk436d94EhMt903o0kqJDBmwTVsK7N3zSxzxkFP QZdR7mqJjAwAdA1x3TqnkBQkTdaTdcUo6hMuOvrsthof5WoFPAy1lFiGNo6gCisSQpz3 Dbb6zUZVgpjMWGeFnD21Oz68wyyuhFkAU8JptPVwR8SW6EkKs+1Xihs7+yiLM4uRtB/u 7GSORGCxPayAKvrS9jMUIe0wh8gWT3azRZixNxkJehzCAbsMdq/D5ONid3ZpGn7IYBiP uIJA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=tTbOgOZL; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id by6si7925172edb.31.2020.09.14.13.30.10; Mon, 14 Sep 2020 13:30:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=tTbOgOZL; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726125AbgINU3Z (ORCPT + 99 others); Mon, 14 Sep 2020 16:29:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37070 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726093AbgINU2K (ORCPT ); Mon, 14 Sep 2020 16:28:10 -0400 Received: from mail-wm1-x342.google.com (mail-wm1-x342.google.com [IPv6:2a00:1450:4864:20::342]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 59710C06178A; Mon, 14 Sep 2020 13:28:09 -0700 (PDT) Received: by mail-wm1-x342.google.com with SMTP id x23so1259376wmi.3; Mon, 14 Sep 2020 13:28:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=QFsgSw1+LH8tFMbI6flA4kr5+81BTDk8dyeIbjo4qWM=; b=tTbOgOZLyOEurC8Hb3O592P2/tTaZtK6L9rND6JdjjPFU7qVyBwh9aCwerAsIBdS/H NUHiNFUoSGnW5/ZLxg12IDub1tT6i5ComZAbDrnVbSlox0kJgR5YGvii6X71dcNh30RR KohoT3SN5FVIyFvk/b/mAXY6NPuT1H2hPwZZ8CResJkzeTDwoJmnbgq7jV5Q0HXo4M/C K0iripgNjjFBYkAgkG/JAfgxOFIkTD9jyUYear6vBEFt9DGDPHW/SbzS8S5CWwh6nL0R c8hCtvK2CSp7x9Sy7fjD/BKpav4CcNHxH6Jm9Y+mrIYR5wRbrqWhJ0gNSwUnyOESiGwX LKWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=QFsgSw1+LH8tFMbI6flA4kr5+81BTDk8dyeIbjo4qWM=; b=cus0EzS44oRvB40pA6DQ8bQSFTt/IGhofCschV5y1QFbXkjEFMUuJ/DcTym/TN2F/Q W71JQsMnMxWfZo0QulQ0bJxGQbgF+4aMyGowDlG8oVRlfytJ98Uv8IEDOqP1ComIi/KI /ibjz375FHiA77yMEbhrsNeU9BImP29L6U0Yvhf2LXfsrrQV6bFnQ3a/tKQQwwG3leCD QfS9t7RpmL99WG5woAbzYqhXp0pnuJAi/hsSWv6TUPjRoAEbv8CptmwJiJml0mmRf+Jp PIWtf6r16aRxbL/Z+qGibJXdY0uZ5+24qZu/37r2BKV2XQefUrc5ElZgS70EQtKJBi7l Zoig== X-Gm-Message-State: AOAM533BfnLpfY0GhN0DS0CMSHrj3/eio2vasi13OBOGeJYeQoQ8/zot VVLprOKxsJ9MR5DukpyUPbM= X-Received: by 2002:a1c:6607:: with SMTP id a7mr1083547wmc.142.1600115287905; Mon, 14 Sep 2020 13:28:07 -0700 (PDT) Received: from localhost.localdomain (oi48z9.static.otenet.gr. [79.129.51.141]) by smtp.gmail.com with ESMTPSA id 92sm24201125wra.19.2020.09.14.13.27.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 14 Sep 2020 13:28:07 -0700 (PDT) From: Cristian Ciocaltea To: Marc Zyngier , Rob Herring , Manivannan Sadhasivam , Thomas Gleixner , Jason Cooper , =?UTF-8?q?Andreas=20F=C3=A4rber?= Cc: parthiban@linumiz.com, Saravanan Sekar , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-actions@lists.infradead.org Subject: [PATCH v7 0/3] Add Actions Semi Owl family sirq support Date: Mon, 14 Sep 2020 23:27:16 +0300 Message-Id: X-Mailer: git-send-email 2.28.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This patch series adds support for the external interrupt controller (SIRQ) found in the Actions Semi Owl family of SoC's (S500, S700 and S900). The controller handles up to 3 external interrupt lines through dedicated SIRQ pins. This is a rework of the patch series submitted some time ago by Parthiban Nallathambi: https://lore.kernel.org/lkml/20181126100356.2840578-1-pn@denx.de/ Please note I have dropped, for the moment, the S700 related patches since I do not own a compatible hardware for testing. I'm using instead an S500 SoC based board for which I have already provided the initial support: https://lore.kernel.org/lkml/cover.1598621459.git.cristian.ciocaltea@gmail.com/ Additionally, I have taken the authorship for the driver patch, considering the original code has been already modified to a great extent and I'm firmly committed to maintaining it in the long run. The SIRQ controller support is a prerequisite of the upcoming MFD driver for the Actions Semi ATC260x PMICs. Thanks and regards, Cristi Changes in v7: - Added Co-developed-by tags to the driver patch according to Marc's review Changes in v6: - Integrated binding doc related feedback from Rob and Marc - Updated cover letter to handle the authorship issue indicated by Mani - Rebased patch series on v5.9-rc4 Changes in v5: - Integrated Marc's review (more details in the driver patch changelog) - Rebased patch series on v5.9-rc1 Changes in v4: - Simplified the DTS structure: * dropped 'actions,sirq-shared-reg' node, now the differentiation between SoC variants is handled via the compatible property * dropped 'actions,sirq-reg-offset', now controller base address in DTS points to SIRQ0 register, so no additional information is required for S500 and S700, while for S900 SoC the offsets of SIRQ1 and SIRQ2 regs are provided by the driver * 'actions,ext-irq-range' was replaced with 'actions,ext-interrupts', an array of the GIC interrupts triggered by the controller - Fixed wrong INTC_EXTCTL_TYPE_MASK definition - Removed redundant irq_fwspec checks in owl_sirq_domain_alloc() - Improved error handling in owl_sirq_of_init() - Added yaml binding document - Dropped S700 related DTS patches for lack of testing hardware: * arm64: dts: actions: Add sirq node for Actions Semi S700 * arm64: dts: actions: s700-cubieboard7: Enable SIRQ - Updated MAINTAINERS - Rebased patchset on kernel v5.8 - Cosmetic changes * Ordered include statements alphabetically * Added comment to owl_sirq_set_type() describing conversion of falling edge or active low signals * Replaced IRQF_TRIGGER_* with corresponding IRQ_TYPE_* variants * Ensured data types and function naming are consistent regarding the 'owl_sirq' prefix Changes in v3 (Parthiban Nallathambi): - Set default operating frequency to 24MHz - Falling edge and Low Level interrupts translated to rising edge and high level - Introduced common function with lock handling for register read and write - Used direct GIC interrupt number for interrupt local hwirq and finding offset using DT entry (range) when registers are shared - Changed irq_ack to irq_eoi - Added translation method for irq_domain_ops - Clearing interrupt pending based on bitmask for edge triggered - Added pinctrl definition for sirq for cubieboard7. This depends on, https://lore.kernel.org/patchwork/patch/1012859/ Changes in v2 (Parthiban Nallathambi): - Added SIRQ as hierarchical chip GIC <----> SIRQ <----> External interrupt controller/Child devices - Device binding updates with vendor prefix - Register sharing handled globally and common init sequence/data for all actions SoC family Cristian Ciocaltea (3): dt-bindings: interrupt-controller: Add Actions SIRQ controller binding irqchip: Add Actions Semi Owl SIRQ controller MAINTAINERS: Add entries for Actions Semi Owl SIRQ controller .../actions,owl-sirq.yaml | 65 ++++ MAINTAINERS | 2 + drivers/irqchip/Makefile | 1 + drivers/irqchip/irq-owl-sirq.c | 359 ++++++++++++++++++ 4 files changed, 427 insertions(+) create mode 100644 Documentation/devicetree/bindings/interrupt-controller/actions,owl-sirq.yaml create mode 100644 drivers/irqchip/irq-owl-sirq.c -- 2.28.0