[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230714074811.GC5194@atomide.com>
Date: Fri, 14 Jul 2023 10:48:11 +0300
From: Tony Lindgren <tony@...mide.com>
To: Johan Hovold <johan+linaro@...nel.org>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Pavel Machek <pavel@....cz>, Len Brown <len.brown@...el.com>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Jiri Slaby <jirislaby@...nel.org>, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-serial@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH 1/3] PM / wakeirq: fix wake irq arming
* Johan Hovold <johan+linaro@...nel.org> [230713 15:01]:
> The decision whether to enable a wake irq during suspend can not be done
> based on the runtime PM state directly as a driver may use wake irqs
> without implementing runtime PM. Such drivers specifically leave the
> state set to the default 'suspended' and the wake irq is thus never
> enabled at suspend.
>
> Add a new wake irq flag to track whether a dedicated wake irq has been
> enabled at runtime suspend and therefore must not be enabled at system
> suspend.
>
> Note that pm_runtime_enabled() can not be used as runtime PM is always
> disabled during late suspend.
Works for me:
Reviewed-by: Tony Lindgren <tony@...mide.com>
Tested-by: Tony Lindgren <tony@...mide.com>
Powered by blists - more mailing lists