From: Joakim Zhang <qiangqing.zhang@nxp.com>
To: tglx@linutronix.de, maz@kernel.org, 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 <qiangqing.zhang@nxp.com>
Subject: [PATCH V2 0/2] irqchip: add NXP INTMUX interrupt controller
Date: Thu, 19 Dec 2019 18:21:03 +0800 [thread overview]
Message-ID: <1576750865-14442-1-git-send-email-qiangqing.zhang@nxp.com> (raw)
Hi Marc,
Registering domain for each channel is indeed a bit unreasonable, I have
changed the driver to support only one channel (channel 0 by default) as
muti-channels is designed to route interrupt to different cores. The fixed
channel is enough for us.
Thanks for your kindly review.
ChangeLog:
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 | 28 ++
drivers/irqchip/Kconfig | 6 +
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-imx-intmux.c | 240 ++++++++++++++++++
4 files changed, 275 insertions(+)
create mode 100644 Documentation/devicetree/bindings/interrupt-controller/fsl,intmux.txt
create mode 100644 drivers/irqchip/irq-imx-intmux.c
--
2.17.1
next reply other threads:[~2019-12-19 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 10:21 Joakim Zhang [this message]
2019-12-19 10:21 ` [PATCH V2 1/2] dt-bindings/irq: add binding for NXP INTMUX interrupt multiplexer Joakim Zhang
2019-12-19 10:21 ` [PATCH V2 2/2] drivers/irqchip: add NXP INTMUX interrupt multiplexer support Joakim Zhang
2019-12-19 12:14 ` [PATCH V2 0/2] irqchip: add NXP INTMUX interrupt controller Marc Zyngier
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=1576750865-14442-1-git-send-email-qiangqing.zhang@nxp.com \
--to=qiangqing.zhang@nxp.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=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
all inboxes | Powered by JetHome®