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 1/3] irqchip/realtek-rtl: use irq_domain_add_linear()
Date: Mon, 19 Sep 2022 22:24:41 +0200 [thread overview]
Message-ID: <0c4cd9f7661a30a4cb7ab9881c4a94bc8a379162.1663617425.git.sander@svanheule.net> (raw)
In-Reply-To: <cover.1663617425.git.sander@svanheule.net>
When using an offset of 0, irq_domain_add_simple() is identical to
irq_domain_add_linear() on DT-based systems, so use the latter instead.
Signed-off-by: Sander Vanheule <sander@svanheule.net>
---
drivers/irqchip/irq-realtek-rtl.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/irqchip/irq-realtek-rtl.c b/drivers/irqchip/irq-realtek-rtl.c
index 56bf502d9c67..160feae0ded7 100644
--- a/drivers/irqchip/irq-realtek-rtl.c
+++ b/drivers/irqchip/irq-realtek-rtl.c
@@ -171,8 +171,7 @@ static int __init realtek_rtl_of_init(struct device_node *node, struct device_no
/* Disable all cascaded interrupts */
writel(0, REG(RTL_ICTL_GIMR));
- domain = irq_domain_add_simple(node, 32, 0,
- &irq_domain_ops, NULL);
+ domain = irq_domain_add_linear(node, 32, &irq_domain_ops, NULL);
ret = map_interrupts(node, domain);
if (ret) {
--
2.37.3
next prev parent 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 [PATCH v6 0/3] Deprecate interrupt-map for realtek-rtl IRQ driver Sander Vanheule
2022-09-19 20:24 ` Sander Vanheule [this message]
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=0c4cd9f7661a30a4cb7ab9881c4a94bc8a379162.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.