From: Marc Zyngier <maz@kernel.org>
To: Jason Cooper <jason@lakedaemon.net>,
Alexandre Torgue <alexandre.torgue@st.com>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
marex@denx.de, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] irqchip/stm32-exti: map direct event to irq parent
Date: Sat, 25 Jul 2020 15:23:31 +0100 [thread overview]
Message-ID: <159568680935.564881.645108348883393903.b4-ty@kernel.org> (raw)
In-Reply-To: <20200717140717.29606-1-alexandre.torgue@st.com>
On Fri, 17 Jul 2020 16:07:17 +0200, Alexandre Torgue wrote:
> EXTI lines are mainly used to wake-up system from CStop low power mode.
> Currently, if a device wants to use a EXTI (direct) line as wakeup line,
> it has to declare 2 interrupts:
> - one for EXTI used to wake-up system (with dedicated_wake_irq api).
> - one for GIC used to get the wake up reason inside the concerned IP.
>
> This split is not really needed as each EXTI line is actually "linked " to
> a GIC. So to avoid this useless double interrupt management in each
> wake-up driver, this patch lets the STM32 EXTI driver abstract it by
> mapping each EXTI line to his corresponding GIC.
Applied to irq/irqchip-5.9, thanks!
[1/1] irqchip/stm32-exti: map direct event to irq parent
commit: 99e05524bc722c8d3c1ab9c817afcb6829dbded3
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2020-07-25 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 14:07 [PATCH v2] irqchip/stm32-exti: map direct event to irq parent Alexandre Torgue
2020-07-25 14:23 ` Marc Zyngier [this message]
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=159568680935.564881.645108348883393903.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marex@denx.de \
--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).