Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp2882960ybl; Thu, 19 Dec 2019 23:41:32 -0800 (PST) X-Google-Smtp-Source: APXvYqx8apUorops/jf8owwcWZLdxpm/IZv8oxTnQ8EBG9E5KPlb+S4s6NckasZLzxHJGM4ixwYu X-Received: by 2002:a9d:4e99:: with SMTP id v25mr13834462otk.363.1576827692626; Thu, 19 Dec 2019 23:41:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576827692; cv=none; d=google.com; s=arc-20160816; b=KtHBPlOhDytDGbaEUw+good/mgUmO4h3nGVS08Z7Yp5atCQZtxY2ZKYZIB/W1qvgx3 Eucny0SnbZKAHF1wYDAeEEtE1C67Our8mvq7F3TfxDpa/lFWrWAwkyc3wJb3EBFDjDzu 0IwQF/Bo1hpQxGxbiR/gsi4kWIrB9/uOV2o1WR3TfUazNT96KfkKfxjt+18xH+WkgTOc TL39Sp5Qo21rqYYuqhmwNjuE0/jjlXqd+3NcOVI8SY3X6pHIwsE1LNXIx/j0cFuNLrDq Ixw5musMOAVFzsj+MHMKKniltKmR5zC6Tn7+G7WLdElF3HJi1NqyhWFO5aCcHLa7p0vU kQiA== 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=QXo+lb2Fjwxf8Yuj96fpEEXpGet6OqlA3jtdiHMg0hc=; b=KYiEkutNxq2daSXJCDkKFrCMW+JTAvPF1aWTb+PCBvmXea6bAQNP8lB2/FRIMTk7s9 HQWEKVkJ7wPnE51SXQCKUEEaWGU+1UFnWJzinYztt1PW39RIUd4HQPMFToT3B4tZ4o3G Smfg39h+3X4inQLSDNf7CzycxoCDgFDU2KObnP+hyV6vveFBTSraytDIuiZLRi0CbNac BuIYB0FrI5nqJgw/jKZvyuUKt9HCq9aH7SyO04JxHVsdfad44iQpHBCAT+zZ3JaESLum 06lSp+v2Fa+Ek9OYzOhul1WumHHTs9aOSC/cV8Uy6yy8uvNW2JuOzvFmSW85Mr84EZdm ssWA== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=nxp.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y140si1670858oia.49.2019.12.19.23.41.19; Thu, 19 Dec 2019 23:41:32 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=nxp.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727135AbfLTHkj (ORCPT + 99 others); Fri, 20 Dec 2019 02:40:39 -0500 Received: from inva021.nxp.com ([92.121.34.21]:39184 "EHLO inva021.nxp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726030AbfLTHkj (ORCPT ); Fri, 20 Dec 2019 02:40:39 -0500 Received: from inva021.nxp.com (localhost [127.0.0.1]) by inva021.eu-rdc02.nxp.com (Postfix) with ESMTP id CCAEA2000A8; Fri, 20 Dec 2019 08:40:37 +0100 (CET) Received: from invc005.ap-rdc01.nxp.com (invc005.ap-rdc01.nxp.com [165.114.16.14]) by inva021.eu-rdc02.nxp.com (Postfix) with ESMTP id A0A3C201225; Fri, 20 Dec 2019 08:40:31 +0100 (CET) Received: from localhost.localdomain (shlinux2.ap.freescale.net [10.192.224.44]) by invc005.ap-rdc01.nxp.com (Postfix) with ESMTP id 4A8114031B; Fri, 20 Dec 2019 15:40:24 +0800 (SGT) From: Joakim Zhang To: maz@kernel.org, tglx@linutronix.de, jason@lakedaemon.net, robh+dt@kernel.org, mark.rutland@arm.com, shawnguo@kernel.org, s.hauer@pengutronix.de Cc: kernel@pengutronix.de, linux-imx@nxp.com, linux-kernel@vger.kernel.org, fugang.duan@nxp.com, linux-arm-kernel@lists.infradead.org, Joakim Zhang Subject: [PATCH V3 0/2] irqchip: add NXP INTMUX interrupt controller Date: Fri, 20 Dec 2019 15:37:09 +0800 Message-Id: <1576827431-31942-1-git-send-email-qiangqing.zhang@nxp.com> X-Mailer: git-send-email 2.7.4 X-Virus-Scanned: ClamAV using ClamSMTP Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Marc, Thanks for your kindly reminder:-), I understood a little more. After adding the .select callback, we can assign an interrupt to one of irq domains from interrupt specifier. Thanks a lot. ChangeLogs: V2->V3: *impletement .xlate and .select callback. V1->V2: *squash patches: drivers/irqchip: enable INTMUX interrupt controller driver drivers/irqchip: add NXP INTMUX interrupt multiplexer support *remove properity "fsl,intmux_chans", only support channel 0 by default. *delete two unused macros. *align the various field in struct intmux_data. *turn to spin lock _irqsave version. *delete struct intmux_irqchip_data. *disable interrupt in probe stage and clear pending status in remove stage. Joakim Zhang (2): dt-bindings/irq: add binding for NXP INTMUX interrupt multiplexer drivers/irqchip: add NXP INTMUX interrupt multiplexer support .../interrupt-controller/fsl,intmux.txt | 36 ++ drivers/irqchip/Kconfig | 6 + drivers/irqchip/Makefile | 1 + drivers/irqchip/irq-imx-intmux.c | 311 ++++++++++++++++++ 4 files changed, 354 insertions(+) create mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,intmux.txt create mode 100644 drivers/irqchip/irq-imx-intmux.c -- 2.17.1