From: Alexandre Torgue <alexandre.torgue@st.com> To: Thomas Gleixner <tglx@linutronix.de>, Jason Cooper <jason@lakedaemon.net>, Marc Zyngier <maz@kernel.org>, Linus Walleij <linus.walleij@linaro.org> Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <linux-gpio@vger.kernel.org>, <marex@denx.de>, <alexandre.torgue@st.com> Subject: [PATCH v3 1/2] irqchip/stm32: Add irq retrigger support Date: Wed, 19 Feb 2020 15:32:28 +0100 [thread overview] Message-ID: <20200219143229.18084-2-alexandre.torgue@st.com> (raw) In-Reply-To: <20200219143229.18084-1-alexandre.torgue@st.com> 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> Tested-by: Marek Vasut <marex@denx.de> diff --git a/drivers/irqchip/irq-stm32-exti.c b/drivers/irqchip/irq-stm32-exti.c index e00f2fa27f00..faa8482c8246 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, -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Torgue <alexandre.torgue@st.com> To: Thomas Gleixner <tglx@linutronix.de>, Jason Cooper <jason@lakedaemon.net>, Marc Zyngier <maz@kernel.org>, Linus Walleij <linus.walleij@linaro.org> Cc: marex@denx.de, linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, alexandre.torgue@st.com Subject: [PATCH v3 1/2] irqchip/stm32: Add irq retrigger support Date: Wed, 19 Feb 2020 15:32:28 +0100 [thread overview] Message-ID: <20200219143229.18084-2-alexandre.torgue@st.com> (raw) In-Reply-To: <20200219143229.18084-1-alexandre.torgue@st.com> 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> Tested-by: Marek Vasut <marex@denx.de> diff --git a/drivers/irqchip/irq-stm32-exti.c b/drivers/irqchip/irq-stm32-exti.c index e00f2fa27f00..faa8482c8246 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, -- 2.17.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-19 14:32 UTC|newest] Thread overview: 26+ 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 ` Alexandre Torgue 2020-02-19 14:32 ` Alexandre Torgue [this message] 2020-02-19 14:32 ` [PATCH v3 1/2] irqchip/stm32: Add irq retrigger support Alexandre Torgue 2020-03-29 20:26 ` [tip: irq/core] " tip-bot2 for Alexandre Torgue 2020-02-19 14:32 ` [PATCH v3 2/2] pinctrl: stm32: Add level interrupt support to gpio irq chip Alexandre Torgue 2020-02-19 14:32 ` Alexandre Torgue 2020-02-20 9:04 ` Linus Walleij 2020-02-20 9:04 ` Linus Walleij 2020-02-20 9:17 ` Marc Zyngier 2020-02-20 9:17 ` Marc Zyngier 2020-03-23 19:04 ` Marek Vasut 2020-03-23 19:04 ` Marek Vasut 2020-03-23 19:19 ` Marek Vasut 2020-03-23 19:19 ` Marek Vasut 2020-03-23 19:31 ` Marc Zyngier 2020-03-23 19:31 ` Marc Zyngier 2020-03-23 19:37 ` Marek Vasut 2020-03-23 19:37 ` Marek Vasut 2020-03-23 19:49 ` Marc Zyngier 2020-03-23 19:49 ` Marc Zyngier 2020-03-23 23:52 ` Marek Vasut 2020-03-23 23:52 ` Marek Vasut 2020-03-23 19:25 ` Marc Zyngier 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=20200219143229.18084-2-alexandre.torgue@st.com \ --to=alexandre.torgue@st.com \ --cc=jason@lakedaemon.net \ --cc=linus.walleij@linaro.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-gpio@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=marex@denx.de \ --cc=maz@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: linkBe 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.