[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c8fe4307-f036-40bd-8d77-b80f19ca8fc2@lunn.ch>
Date: Mon, 28 Jul 2025 19:12:08 +0200
From: Andrew Lunn <andrew@...n.ch>
To: "Russell King (Oracle)" <rmk+kernel@...linux.org.uk>
Cc: Heiner Kallweit <hkallweit1@...il.com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
linux-arm-kernel@...ts.infradead.org,
linux-stm32@...md-mailman.stormreply.com,
Maxime Coquelin <mcoquelin.stm32@...il.com>, netdev@...r.kernel.org,
Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH RFC net-next 5/7] net: stmmac: use core wake IRQ support
> - if (wol->wolopts) {
> - device_set_wakeup_enable(priv->device, 1);
> - /* Avoid unbalanced enable_irq_wake calls */
> - if (priv->wol_irq_disabled)
> - enable_irq_wake(priv->wol_irq);
> - priv->wol_irq_disabled = false;
> - } else {
> - device_set_wakeup_enable(priv->device, 0);
> - /* Avoid unbalanced disable_irq_wake calls */
> - if (!priv->wol_irq_disabled)
> - disable_irq_wake(priv->wol_irq);
> - priv->wol_irq_disabled = true;
> - }
> + device_set_wakeup_enable(priv->device, !!wol->wolopts);
It might be worth mentioning in the commit message that
device_set_wakeup_enable() does not care about unbalanced calls to
enable/disable. This obviously caused issues in the past with
enable_irq_wake()/disable_irq_wake().
Andrew
Powered by blists - more mailing lists