From: Talel Shenhar <talel@amazon.com>
To: nicolas.ferre@microchip.com, jason@lakedaemon.net,
marc.zyngier@arm.com, mark.rutland@arm.com,
mchehab+samsung@kernel.org, robh+dt@kernel.org,
davem@davemloft.net, shawn.lin@rock-chips.com,
tglx@linutronix.de, devicetree@vger.kernel.org,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Cc: dwmw@amazon.co.uk, benh@kernel.crashing.org, jonnyc@amazon.com,
hhhawa@amazon.com, ronenk@amazon.com, hanochu@amazon.com,
barakw@amazon.com, Talel Shenhar <talel@amazon.com>
Subject: [PATCH v4 0/2] Amazon's Annapurna Labs Fabric Interrupt Controller
Date: Mon, 10 Jun 2019 11:34:41 +0300 [thread overview]
Message-ID: <1560155683-29584-1-git-send-email-talel@amazon.com> (raw)
This series introduces support for Amazon's Annapurna Labs Fabric Interrupt
Controller.
The Amazon's Annapurna Labs FIC (Fabric Interrupt Controller) has 32
inputs/sources. This FIC may be cascaded into another FIC or connected
directly to the main CPU Interrupt Controller (e.g. GIC).
Changes since v3:
=================
- tightened the verification for supported trigger types
- updated dt-binding's example to meet the binding description
(interrupt-cells to 2)
- added description to interrupt-cells to explain each field
- changed pr_err to pr_debug inside al_fic_irq_set_type in order to allow
the user to enable printouts for verbose information in case of errors
Changes since v2:
=================
- updated dt-bindings to use proper format for entry name
- removed kernel-doc format style from Copyright
- removed unneeded/misplaced selects from Kconfig
- changed used mmio operation to relaxed flavor
- changed error return value from EPERM to EINVAL int case of attempting to
reconfigure the FIC after it has been configured
- fixed commenting format
- used drivers define instead of subsystem internals
- moved al_fic_hw_init function to caller
- removed al_fic_wire_get_domain from documentation
- removed argument validation from al_fic_wire_init
Changes since v1:
=================
- removing unused exported APIs
- updating cover letter and commit message accordingly
Talel Shenhar (2):
dt-bindings: interrupt-controller: Amazon's Annapurna Labs FIC
irqchip: al-fic: Introduce Amazon's Annapurna Labs Fabric Interrupt
Controller Driver
.../interrupt-controller/amazon,al-fic.txt | 29 +++
MAINTAINERS | 6 +
drivers/irqchip/Kconfig | 8 +
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-al-fic.c | 278 +++++++++++++++++++++
5 files changed, 322 insertions(+)
create mode 100644 Documentation/devicetree/bindings/interrupt-controller/amazon,al-fic.txt
create mode 100644 drivers/irqchip/irq-al-fic.c
--
2.7.4
next reply other threads:[~2019-06-10 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 8:34 Talel Shenhar [this message]
2019-06-10 8:34 ` [PATCH v4 1/2] dt-bindings: interrupt-controller: Amazon's Annapurna Labs FIC Talel Shenhar
2019-06-18 10:46 ` Marc Zyngier
2019-07-09 2:23 ` Rob Herring
2019-07-09 5:59 ` Shenhar, Talel
2019-07-09 8:15 ` Marc Zyngier
2019-07-09 8:17 ` Shenhar, Talel
2019-07-09 13:25 ` Rob Herring
2019-06-10 8:34 ` [PATCH v4 2/2] irqchip: al-fic: Introduce Amazon's Annapurna Labs Fabric Interrupt Controller Driver Talel Shenhar
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=1560155683-29584-1-git-send-email-talel@amazon.com \
--to=talel@amazon.com \
--cc=barakw@amazon.com \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hanochu@amazon.com \
--cc=hhhawa@amazon.com \
--cc=jason@lakedaemon.net \
--cc=jonnyc@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=ronenk@amazon.com \
--cc=shawn.lin@rock-chips.com \
--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).