From: Dhruva Gole <d-gole@ti.com>
To: Qingliang Li <qingliang.li@mediatek.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Johan Hovold <johan+linaro@kernel.org>,
Tony Lindgren <tony@atomide.com>, Dhruva Gole <d-gole@ti.com>
Cc: <linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH] PM: wakeirq: fix wake irq warning in system suspend stage
Date: Wed, 28 Feb 2024 11:34:23 +0530 [thread overview]
Message-ID: <1390e743-2216-4435-b2ef-7d92a55605b1@ti.com> (raw)
In-Reply-To: <20240228020040.25815-1-qingliang.li@mediatek.com>
Hi,
On 28/02/24 07:30, Qingliang Li wrote:
> When driver registers the wake irq with reverse enable ordering,
> the wake irq will be re-enabled when entering system suspend, triggering
> an 'Unbalanced enable for IRQ xxx' warning. The wake irq will be
> enabled in both dev_pm_enable_wake_irq_complete() and dev_pm_arm_wake_irq()
>
> To fix this issue, complete the setting of WAKE_IRQ_DEDICATED_ENABLED flag
> in dev_pm_enable_wake_irq_complete() to avoid redundant irq enablement.
Just trying to understand, why not in dev_pm_arm_wake_irq ?
Is it cuz it's called much after dev_pm_enable_wake_irq_complete ?
Not sure what's the exact call order, but I am assuming
dev_pm_enable_wake_irq_complete is more of a runtime thing and
dev_pm_arm_wake_irq happens finally at system suspend?
>
> Fixes: 8527beb12087 ("PM: sleep: wakeirq: fix wake irq arming")
> Signed-off-by: Qingliang Li <qingliang.li@mediatek.com>
> ---
$subject: Most recent convention used for this file is:
"PM: sleep: wakeirq: ..."
> drivers/base/power/wakeirq.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/base/power/wakeirq.c b/drivers/base/power/wakeirq.c
> index 42171f766dcb..5a5a9e978e85 100644
> --- a/drivers/base/power/wakeirq.c
> +++ b/drivers/base/power/wakeirq.c
> @@ -313,8 +313,10 @@ void dev_pm_enable_wake_irq_complete(struct device *dev)
> return;
>
> if (wirq->status & WAKE_IRQ_DEDICATED_MANAGED &&
> - wirq->status & WAKE_IRQ_DEDICATED_REVERSE)
> + wirq->status & WAKE_IRQ_DEDICATED_REVERSE) {
> enable_irq(wirq->irq);
> + wirq->status |= WAKE_IRQ_DEDICATED_ENABLED;
> + }
But this does make sense to make sure status is updated,
You can pick my R-by.
Reviewed-by: Dhruva Gole <d-gole@ti.com>
--
Thanks and Regards,
Dhruva Gole
next prev parent reply other threads:[~2024-02-28 6:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 2:00 [PATCH] PM: wakeirq: fix wake irq warning in system suspend stage Qingliang Li
2024-02-28 6:04 ` Dhruva Gole [this message]
2024-02-28 8:33 ` Qingliang Li (黎晴亮)
2024-02-28 8:58 ` Dhruva Gole
2024-02-29 19:31 ` Rafael J. Wysocki
2024-02-28 6:07 ` Greg Kroah-Hartman
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=1390e743-2216-4435-b2ef-7d92a55605b1@ti.com \
--to=d-gole@ti.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan+linaro@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=pavel@ucw.cz \
--cc=qingliang.li@mediatek.com \
--cc=rafael@kernel.org \
--cc=tony@atomide.com \
/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