From: Eliav Farber <farbere@amazon.com>
To: Thomas Gleixner <tglx@kernel.org>, Talel Shenhar <talel@amazon.com>
Cc: Radu Rendec <radu@rendec.net>, Rob Herring <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"Eliav Farber" <farbere@amazon.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/8] irqchip/al-fic: shared parent IRQ, error/fatal outputs and affinity
Date: Sun, 27 Sep 2026 08:06:29 +0000 [thread overview]
Message-ID: <20260927080637.27285-1-farbere@amazon.com> (raw)
This series extends the Amazon Annapurna Labs Fabric Interrupt Controller
(FIC) driver to support newer hardware revisions found on later Annapurna
Labs SoCs, plus a few smaller fixes and cleanups.
The block the driver calls a FIC is the generic Annapurna Labs interrupt
controller, built from groups of up to 32 triggers each. A device tree node
describes one group, not a whole controller, and the groups of one
controller share that controller's output line toward the parent GIC SPI.
Later revisions add two interrupt outputs on top of the original "info"
output - an "error" output and a "fatal" output - each with its own mask
register. Which output a group drives is fixed when the SoC is wired.
The series is organised as follows:
1. Fix an argument alignment and a repeated word flagged by checkpatch.
No functional change.
2. Use %pOF in log messages and raise the successful-init message to
pr_info, so each FIC instance is identifiable at boot.
3. Keep the device_node in struct al_fic instead of a cached name string
that aliased node storage.
4. Request the parent interrupt as shared (IRQF_SHARED) instead of a
chained handler, so the several nodes of one controller can share one
GIC SPI.
5. Extend the binding with an optional amazon,al-fic-mask property
(info, error or fatal; default info) selecting which output a group
drives.
6. Add error/fatal output support and FIC v2: version detection from the
control register, the two extra mask registers, and a mask_cache
workaround for a v2 erratum where the error and fatal mask registers
always read back as 0.
7. Add FIC v3 support. v3 shares v2's group layout but fixes the mask
read-back erratum, so the v2 workaround is deliberately not applied.
8. Add an irq_set_affinity callback so drivers that call
irq_set_affinity() (which fails with -EINVAL when the irqchip has no
such callback) can probe when routed through a FIC instance.
Patches 4 and 8 are co-developed with Talel Shenhar, the al-fic driver
maintainer, and carry his Signed-off-by.
Changes since v1:
- Binding (patch 5): drop the two proposed per-output compatible strings
(amazon,al-fic-error / amazon,al-fic-fatal). A node describes one group
and a controller reports its revision in the group control register
(bits 29-28), so no per-revision or per-output compatible is needed.
Instead select the output with a new optional amazon,al-fic-mask
property (info, error, fatal; default info), which keeps existing
amazon,al-fic nodes behaving as before. This addresses Conor Dooley's
review of the v1 binding patch, and the commit message now describes
the hardware and the group granularity as he asked. The YAML gains an
example fragment.
- FIX (patch 4): the request_irq() error path called
irq_free_generic_chip(gc), which is kfree(gc) on an interior pointer
into a single allocation - invalid free, reachable when request_irq()
fails at probe. Replace it with irq_domain_remove_generic_chips()
before irq_domain_remove().
- FIX (patch 6): the v2 mask_cache workaround was dead. mask_cache is not
seeded until the first child mapping, so the override was overwritten
with 0 and the first unmask then cleared the whole mask register,
unmasking all 32 sources. Drop IRQ_GC_INIT_MASK_CACHE for the error and
fatal outputs and seed mask_cache from the value the driver programmed.
- New patch 1: checkpatch cleanup (alignment + repeated word), at the head
of the series.
- New patch 3: keep the device_node rather than a cached name string;
reorders the irqchip prep so every commit builds on its own.
- Reworded commit messages throughout to describe hardware rather than
device tree mechanics.
v1: https://lore.kernel.org/all/20260924062311.37308-1-farbere@amazon.com/
Eliav Farber (8):
irqchip/al-fic: fix argument alignment and a repeated word
irqchip/al-fic: use %pOF and raise init log level
irqchip/al-fic: keep the device_node instead of a cached name string
irqchip/al-fic: switch to shared parent interrupt
dt-bindings: interrupt-controller: amazon,al-fic: add mask selection
irqchip/al-fic: support error and fatal outputs and FIC v2
irqchip/al-fic: add support for FIC v3
irqchip/al-fic: add irq_set_affinity callback
.../interrupt-controller/amazon,al-fic.yaml | 16 +-
drivers/irqchip/irq-al-fic.c | 233 ++++++++++++++----
2 files changed, 206 insertions(+), 43 deletions(-)
base-commit: 6828157ab3e96cd1c957b78d995c5e508a2eb2c2
--
2.47.3
next reply other threads:[~2026-09-27 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-27 8:06 Eliav Farber [this message]
2026-09-27 8:06 ` [PATCH v2 1/8] irqchip/al-fic: fix argument alignment and a repeated word Eliav Farber
2026-09-27 8:06 ` [PATCH v2 2/8] irqchip/al-fic: use %pOF and raise init log level Eliav Farber
2026-09-27 8:06 ` [PATCH v2 3/8] irqchip/al-fic: keep the device_node instead of a cached name string Eliav Farber
2026-09-27 8:06 ` [PATCH v2 4/8] irqchip/al-fic: switch to shared parent interrupt Eliav Farber
2026-09-27 8:06 ` [PATCH v2 5/8] dt-bindings: interrupt-controller: amazon,al-fic: add mask selection Eliav Farber
2026-09-28 16:50 ` Conor Dooley
2026-09-27 8:06 ` [PATCH v2 6/8] irqchip/al-fic: support error and fatal outputs and FIC v2 Eliav Farber
2026-09-27 8:06 ` [PATCH v2 7/8] irqchip/al-fic: add support for FIC v3 Eliav Farber
2026-09-27 8:06 ` [PATCH v2 8/8] irqchip/al-fic: add irq_set_affinity callback Eliav Farber
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=20260927080637.27285-1-farbere@amazon.com \
--to=farbere@amazon.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=radu@rendec.net \
--cc=robh@kernel.org \
--cc=talel@amazon.com \
--cc=tglx@kernel.org \
/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®