[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87imcmj9q5.fsf@nanos.tec.linutronix.de>
Date: Thu, 10 Sep 2020 10:51:14 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Doug Anderson <dianders@...omium.org>
Cc: Maulik Shah <mkshah@...eaurora.org>,
Stephen Boyd <swboyd@...omium.org>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Evan Green <evgreen@...omium.org>,
LinusW <linus.walleij@...aro.org>, Marc Zyngier <maz@...nel.org>,
Matthias Kaehlcke <mka@...omium.org>,
LKML <linux-kernel@...r.kernel.org>,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
"open list\:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
Andy Gross <agross@...nel.org>,
Jason Cooper <jason@...edaemon.net>,
Rajendra Nayak <rnayak@...eaurora.org>,
Lina Iyer <ilina@...eaurora.org>,
Srinivas Rao L <lsrao@...eaurora.org>,
"Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: [PATCH v5 3/6] genirq/PM: Introduce IRQCHIP_ENABLE_WAKEUP_ON_SUSPEND flag
On Tue, Sep 08 2020 at 12:05, Doug Anderson wrote:
> On Fri, Sep 4, 2020 at 2:54 AM Thomas Gleixner <tglx@...utronix.de> wrote:
>> Right and that's where we want the new chip flag with the unmask if
>> armed.
>
> OK, so we're back in Maulik's court to spin, right? I think the last
> word before our tangent was at:
>
> http://lore.kernel.org/r/87y2m1vhkm.fsf@nanos.tec.linutronix.de
>
> There you were leaning towards #2 ("a new function
> disable_wakeup_irq_for_suspend()"). Presumably you'd now be
> suggesting #1 ("Do the symmetric thing") since I've pointed out the
> bunch of drivers that would need to change.
Yes #1 is what we need.
Thanks,
tglx
Powered by blists - more mailing lists