From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Daniel Braunwarth <daniel.braunwarth@kuka.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Gatien CHEVALLIER <gatien.chevallier@foss.st.com>,
Jakub Kicinski <kuba@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Thierry Reding <treding@nvidia.com>
Subject: Re: [PATCH RFC ???net???] net: phy: realtek: fix wake-on-lan support
Date: Wed, 30 Jul 2025 16:49:45 +0100 [thread overview]
Message-ID: <aIo_GW9zvPzLd0zs@shell.armlinux.org.uk> (raw)
In-Reply-To: <2842a6b1-ba65-4f7c-8699-aa2fd3de85b0@lunn.ch>
On Wed, Jul 30, 2025 at 04:35:45PM +0200, Andrew Lunn wrote:
> > Not all interrupts are capable of waking the system up, and there is
> > no way for a PHY to know whether it's connected to an interrupt that
> > has that ability.
>
> I was wondering about that. And maybe that enable_irq_wake() returns
> -EOPNOTSUPP if it cannot actually wake the system? But there is no
> documentation about that.
,,, and that means we can't use the wakeirq helpers.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2025-07-30 15:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 8:35 [PATCH RFC ???net???] net: phy: realtek: fix wake-on-lan support Russell King (Oracle)
2025-07-30 13:59 ` Andrew Lunn
2025-07-30 14:22 ` Russell King (Oracle)
2025-07-30 14:35 ` Andrew Lunn
2025-07-30 15:49 ` Russell King (Oracle) [this message]
2025-07-30 14:24 ` Gatien CHEVALLIER
2025-07-30 14:52 ` Andrew Lunn
2025-07-30 15:03 ` Daniel Braunwarth
2025-07-30 18:45 ` Florian Fainelli
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=aIo_GW9zvPzLd0zs@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=daniel.braunwarth@kuka.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=gatien.chevallier@foss.st.com \
--cc=hkallweit1@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=treding@nvidia.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;
as well as URLs for NNTP newsgroup(s).