From: Joakim Zhang <qiangqing.zhang@nxp.com>
To: "maz@kernel.org" <maz@kernel.org>,
"jason@lakedaemon.net" <jason@lakedaemon.net>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"robh@kernel.org" <robh@kernel.org>
Cc: "kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
dl-linux-imx <linux-imx@nxp.com>, Andy Duan <fugang.duan@nxp.com>
Subject: [PATCH V6 0/2] irqchip: add NXP INTMUX interrupt controller
Date: Fri, 17 Jan 2020 06:10:00 +0000 [thread overview]
Message-ID: <20200117060653.27485-1-qiangqing.zhang@nxp.com> (raw)
This patch set adds driver for NXP INTMUX interrupt controller.
ChangeLogs:
V5->V6:
*fix DTC check failure from binding file.
V4->V5:
*get number of channels by platform_irq_count() instead of
'fsl,intmux_chans' property
*update binding files and remove 'fsl,intmux_chans' property.
V3->V4:
*set IRQ_TYPE_LEVEL_HIGH flag in .xlate callback.
*fix comment format.
*use an intermediate variable for irq_domain_add_linear().
*disable interrupts before enabling chained interrupt.
*disable interrupt in imx_remove() for level interrupt.
*convert binding to DT schema.
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.yaml | 68 ++++
drivers/irqchip/Kconfig | 6 +
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-imx-intmux.c | 309 ++++++++++++++++++
4 files changed, 384 insertions(+)
create mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,intmux.yaml
create mode 100644 drivers/irqchip/irq-imx-intmux.c
--
2.17.1
next reply other threads:[~2020-01-17 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 6:10 Joakim Zhang [this message]
2020-01-17 6:10 ` [PATCH V6 1/2] dt-bindings/irq: add binding for NXP INTMUX interrupt multiplexer Joakim Zhang
2020-01-17 16:37 ` Rob Herring
2020-01-17 6:10 ` [PATCH V6 2/2] drivers/irqchip: add NXP INTMUX interrupt multiplexer support Joakim Zhang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200117060653.27485-1-qiangqing.zhang@nxp.com \
--to=qiangqing.zhang@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=jason@lakedaemon.net \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).