From: David Daney <david.daney@cavium.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, David Daney <david.daney@cavium.com>
Subject: [PATCH v3 0/6] genirq/gpio: Add driver for ThunderX and OCTEON-TX SoCs
Date: Tue, 14 Feb 2017 09:49:30 -0800 [thread overview]
Message-ID: <1487094576-229208-1-git-send-email-david.daney@cavium.com> (raw)
Per the Subject: Add driver for ThunderX and OCTEON-TX SoCs
This GPIO hardware looks like a PCIe device, with the interrupt signal
from each GPIO line being routed to a dedicated MSI-X. This interrupt
routing requires that we add some custom processing to the beginning
of the MSI-X irqdomain hierarchy.
Changes from v2:
- in 4/6: Added Rob Harring's Acked-by
- Added three patches to genirq/irqdomain to support interrupt code
in the driver.
- Rewrite irq code in driver to use irqdomain hierarchy.
- Other naming and style changes as recommended by Linus Walleij.
Changes from v1:
- in 1/3: Addressed Rob Harring's comments.
- in 2/3: Trivial cleanups found in internal review + add some
comments.
David Daney (6):
genirq: Export more irq_chip_*_parent() functions.
genirq: Add handle_fasteoi_{level,edge}_irq flow handlers.
irqdomain: Add irq_domain_{push,pop}_irq() functions.
dt-bindings: gpio: Add binding documentation for gpio-thunderx
gpio: Add gpio driver support for ThunderX and OCTEON-TX
MAINTAINERS: Add entry for THUNDERX GPIO Driver.
.../devicetree/bindings/gpio/gpio-thunderx.txt | 27 ++
MAINTAINERS | 5 +
drivers/gpio/Kconfig | 7 +
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-thunderx.c | 490 +++++++++++++++++++++
include/linux/irq.h | 2 +
include/linux/irqdomain.h | 3 +
kernel/irq/chip.c | 105 +++++
kernel/irq/irqdomain.c | 137 ++++++
9 files changed, 777 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/gpio-thunderx.txt
create mode 100644 drivers/gpio/gpio-thunderx.c
--
1.8.3.1
next reply other threads:[~2017-02-14 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 17:49 David Daney [this message]
2017-02-14 17:49 ` [PATCH v3 1/6] genirq: Export more irq_chip_*_parent() functions David Daney
2017-02-14 17:49 ` [PATCH v3 2/6] genirq: Add handle_fasteoi_{level,edge}_irq flow handlers David Daney
2017-02-14 17:49 ` [PATCH v3 3/6] irqdomain: Add irq_domain_{push,pop}_irq() functions David Daney
2017-02-14 17:49 ` [PATCH v3 4/6] dt-bindings: gpio: Add binding documentation for gpio-thunderx David Daney
2017-02-14 17:49 ` [PATCH v3 5/6] gpio: Add gpio driver support for ThunderX and OCTEON-TX David Daney
2017-02-15 11:11 ` kbuild test robot
2017-02-14 17:49 ` [PATCH v3 6/6] MAINTAINERS: Add entry for THUNDERX GPIO Driver David Daney
2017-02-15 19:29 ` [PATCH v3 0/6] genirq/gpio: Add driver for ThunderX and OCTEON-TX SoCs David Daney
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=1487094576-229208-1-git-send-email-david.daney@cavium.com \
--to=david.daney@cavium.com \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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).