linux-kernel - Re: [PATCH v2] irqchip/stm32-exti: map direct event to irq parent

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <159568680935.564881.645108348883393903.b4-ty@kernel.org>
Date:   Sat, 25 Jul 2020 15:23:31 +0100
From:   Marc Zyngier <maz@...nel.org>
To:     Jason Cooper <jason@...edaemon.net>,
        Alexandre Torgue <alexandre.torgue@...com>,
        Thomas Gleixner <tglx@...utronix.de>
Cc:     linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
        marex@...x.de, linux-stm32@...md-mailman.stormreply.com,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2] irqchip/stm32-exti: map direct event to irq parent

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.