From: "tip-bot2 for Alexandre Torgue" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Alexandre Torgue <alexandre.torgue@st.com>,
Marc Zyngier <maz@kernel.org>, Marek Vasut <marex@denx.de>,
x86 <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [tip: irq/core] irqchip/stm32: Add irq retrigger support
Date: Sun, 29 Mar 2020 20:26:24 -0000 [thread overview]
Message-ID: <158551358456.28353.6069975380249902216.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20200219143229.18084-2-alexandre.torgue@st.com>
The following commit has been merged into the irq/core branch of tip:
Commit-ID: 25591d4c6459ce416a319832ce806be7b86183dc
Gitweb: https://git.kernel.org/tip/25591d4c6459ce416a319832ce806be7b86183dc
Author: Alexandre Torgue <alexandre.torgue@st.com>
AuthorDate: Wed, 19 Feb 2020 15:32:28 +01:00
Committer: Marc Zyngier <maz@kernel.org>
CommitterDate: Sun, 08 Mar 2020 14:25:45
irqchip/stm32: Add irq retrigger support
This commit introduces retrigger support for stm32_ext_h chip.
It consists to rise the GIC interrupt mapped to an EXTI line.
Signed-off-by: Alexandre Torgue <alexandre.torgue@st.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Tested-by: Marek Vasut <marex@denx.de>
Link: https://lore.kernel.org/r/20200219143229.18084-2-alexandre.torgue@st.com
---
drivers/irqchip/irq-stm32-exti.c | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/drivers/irqchip/irq-stm32-exti.c b/drivers/irqchip/irq-stm32-exti.c
index e00f2fa..faa8482 100644
--- a/drivers/irqchip/irq-stm32-exti.c
+++ b/drivers/irqchip/irq-stm32-exti.c
@@ -604,12 +604,24 @@ static void stm32_exti_h_syscore_deinit(void)
unregister_syscore_ops(&stm32_exti_h_syscore_ops);
}
+static int stm32_exti_h_retrigger(struct irq_data *d)
+{
+ struct stm32_exti_chip_data *chip_data = irq_data_get_irq_chip_data(d);
+ const struct stm32_exti_bank *stm32_bank = chip_data->reg_bank;
+ void __iomem *base = chip_data->host_data->base;
+ u32 mask = BIT(d->hwirq % IRQS_PER_BANK);
+
+ writel_relaxed(mask, base + stm32_bank->swier_ofst);
+
+ return 0;
+}
+
static struct irq_chip stm32_exti_h_chip = {
.name = "stm32-exti-h",
.irq_eoi = stm32_exti_h_eoi,
.irq_mask = stm32_exti_h_mask,
.irq_unmask = stm32_exti_h_unmask,
- .irq_retrigger = irq_chip_retrigger_hierarchy,
+ .irq_retrigger = stm32_exti_h_retrigger,
.irq_set_type = stm32_exti_h_set_type,
.irq_set_wake = stm32_exti_h_set_wake,
.flags = IRQCHIP_MASK_ON_SUSPEND,
next prev parent reply other threads:[~2020-03-29 20:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 14:32 [PATCH v3 0/2] Add GPIO level-sensitive interrupt support Alexandre Torgue
2020-02-19 14:32 ` [PATCH v3 1/2] irqchip/stm32: Add irq retrigger support Alexandre Torgue
2020-03-29 20:26 ` tip-bot2 for Alexandre Torgue [this message]
2020-02-19 14:32 ` [PATCH v3 2/2] pinctrl: stm32: Add level interrupt support to gpio irq chip Alexandre Torgue
2020-02-20 9:04 ` Linus Walleij
2020-02-20 9:17 ` Marc Zyngier
2020-03-23 19:04 ` Marek Vasut
2020-03-23 19:19 ` Marek Vasut
2020-03-23 19:31 ` Marc Zyngier
2020-03-23 19:37 ` Marek Vasut
2020-03-23 19:49 ` Marc Zyngier
2020-03-23 23:52 ` Marek Vasut
2020-03-23 19:25 ` Marc Zyngier
2020-03-29 20:26 ` [tip: irq/core] " tip-bot2 for Alexandre Torgue
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=158551358456.28353.6069975380249902216.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=alexandre.torgue@st.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=marex@denx.de \
--cc=maz@kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).