mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Magnus Leatti <magnusleatti@kernelriot.com>
To: Yao Zi <me@ziyao.cc>, Andrew Lunn <andrew@lunn.ch>
Cc: Maxime Chevallier <maxime.chevallier@bootlin.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Giuseppe Nespolino <g.nespolino@gmail.com>,
	netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net: stmmac: dwmac-motorcomm: support Wake-on-LAN from S5
Date: Thu, 19 Nov 2026 14:58:22 -0300	[thread overview]
Message-ID: <20261119175822.1033074-1-magnusleatti@kernelriot.com> (raw)
In-Reply-To: <avwr7G83tUvZ1HP2@pie>

Hi Yao and Andrew,

On Tue, Nov 17, 2026 at 10:26:52AM +0000, Yao Zi wrote:
> I think it's likely not BIOS setting this up, since the chip's behavior
> is the same when a reset is manually triggered, according to Magnus'
> test.

Fair: BIOS ran before my dump, but if I trigger SYS_RESET from Linux
with no driver, the chip behaves the same: OOB_WOL_CTRL_DIS clear,
GMAC_PMT = 3 (power_down | magic_pkt_en), eFuse MAC in filter 0,
WOL_CTRL_PKT_EN clear. No BIOS involvement, and v2 counts on that

Yao, on power failure: yup... it fails to wake. I tested it today with
the v2 module and "wol g", BIOS set to stay off when the power comes
back:

  power-off                 wake on the eFuse address
  power-off, cable out, in  stays off, no wake in 4 min of magic packets

So if power drops, it just won't wake until it's been shut down cleanly
through the driver again.

FWIW the vendor driver does the same: wakes after a normal power-off,
sleeps through everything after a power loss. So its the hardware and
not something a driver can fix.

Thank you both for your time! I will be sending V2 in the upcoming days.

Magnus

  reply	other threads:[~2026-11-19 17:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16  9:17 [PATCH net-next 0/2] net: stmmac: dwmac-motorcomm: shutdown hook and " Magnus Leatti
2026-11-16  9:17 ` [PATCH net-next 1/2] net: stmmac: dwmac-motorcomm: quiesce the device at shutdown Magnus Leatti
2026-11-16 14:33   ` Yao Zi
2026-11-16 14:58     ` Magnus Leatti
2026-11-18  9:18   ` netdev-bot+sashiko
2026-11-16  9:17 ` [PATCH net-next 2/2] net: stmmac: dwmac-motorcomm: support Wake-on-LAN from S5 Magnus Leatti
2026-11-16 15:08   ` Yao Zi
2026-11-16 15:17     ` Yao Zi
2026-11-16 16:48       ` Magnus Leatti
2026-11-16 17:26         ` Yao Zi
2026-11-17  1:27         ` Andrew Lunn
2026-11-17 10:26           ` Yao Zi
2026-11-19 17:58             ` Magnus Leatti [this message]
2026-11-18  9:18   ` netdev-bot+sashiko
2026-11-16 11:23 ` [PATCH net-next 0/2] net: stmmac: dwmac-motorcomm: shutdown hook and " Giuseppe Nespolino
2026-11-16 11:36   ` Magnus Leatti

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=20261119175822.1033074-1-magnusleatti@kernelriot.com \
    --to=magnusleatti@kernelriot.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=g.nespolino@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=me@ziyao.cc \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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

all inboxes | Powered by JetHome®