From: Sander Vanheule <sander@svanheule.net>
To: Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Sander Vanheule <sander@svanheule.net>
Subject: [PATCH v6 0/3] Deprecate interrupt-map for realtek-rtl IRQ driver
Date: Mon, 19 Sep 2022 22:24:40 +0200 [thread overview]
Message-ID: <cover.1663617425.git.sander@svanheule.net> (raw)
The original implementation for this interrupt controller/router used
an interrupt-map parser to determine which parent interrupts were
present. However, this controller is not transparent, so a list of
parent interrupts seems more appropriate, while also getting rid of the
assumed routing to parent interrupts.
Changes since v5:
Link: https://lore.kernel.org/all/cover.1644864700.git.sander@svanheule.net/
- Allow interrupt-map for new compatibles, but mark as deprecated
- Change back to single-cell interrupt specifiers
- Drop patch adding a domain for every output line
Changes since v4:
Link: https://lore.kernel.org/all/cover.1644165421.git.sander@svanheule.net/
- Add Rob's Reviewed-by
- Use irq_domain_add_linear instead of irq_domain_add_simple
- Drop 'inline' specifiers from static functions
- Drop WARN in intc_select() to only warn once for old bindings
Changes since v3:
Link: https://lore.kernel.org/all/cover.1641739718.git.sander@svanheule.net/
- Patches with fixes were merged, so these are no longer included.
- Update the devicetree changes to more clearly indicate the controller
is not transparent.
Changes since v2 (RFC):
Link: https://lore.kernel.org/all/cover.1640548009.git.sander@svanheule.net/
- Define new, two-part compatibles for devicetree bindings. The existing format
is kept for the old one-part compatible, but deprecated. New compatibles will
require a different way of specifying parent interrupts and interrupt routing.
- Add change to handle all pending SoC interrupts in one go.
Changes since v1 (RFC):
Link: https://lore.kernel.org/all/cover.1640261161.git.sander@svanheule.net/
- Split some of the changes to limit the patch scope to one issue.
- Dropped some small (spurious or unneeded) changes
- Instead of dropping/replacing interrupt-map, the last patches now provide an
implementation that amends the current situtation.
Sander Vanheule (3):
irqchip/realtek-rtl: use irq_domain_add_linear
dt-bindings: interrupt-controller: realtek,rtl-intc: require parents
irqchip/realtek-rtl: use parent interrupts
.../realtek,rtl-intc.yaml | 60 ++++++--
drivers/irqchip/irq-realtek-rtl.c | 134 ++++++++----------
2 files changed, 106 insertions(+), 88 deletions(-)
--
2.37.3
next reply other threads:[~2022-09-19 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 20:24 Sander Vanheule [this message]
2022-09-19 20:24 ` [PATCH v6 1/3] irqchip/realtek-rtl: use irq_domain_add_linear() Sander Vanheule
2022-09-19 20:24 ` [PATCH v6 2/3] dt-bindings: interrupt-controller: realtek,rtl-intc: require parents Sander Vanheule
2022-09-23 18:33 ` Krzysztof Kozlowski
2022-09-26 19:25 ` Rob Herring
2022-09-19 20:24 ` [PATCH v6 3/3] irqchip/realtek-rtl: use parent interrupts Sander Vanheule
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=cover.1663617425.git.sander@svanheule.net \
--to=sander@svanheule.net \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--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).