Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yao Zi <me@ziyao.cc>
To: Andrew Lunn <andrew@lunn.ch>,
	Magnus Leatti <magnusleatti@kernelriot.com>
Cc: me@ziyao.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: Tue, 17 Nov 2026 10:26:52 +0000	[thread overview]
Message-ID: <avwr7G83tUvZ1HP2@pie> (raw)
In-Reply-To: <84566846-2ddd-471d-8f4f-068ef10f522d@lunn.ch>

On Tue, Nov 17, 2026 at 02:27:07AM +0100, Andrew Lunn wrote:
> On Mon, Nov 16, 2026 at 01:48:47PM -0300, Magnus Leatti wrote:
> > Hi Yao,
> > 
> > On Mon, Nov 16, 2026 at 03:17:00PM +0000, Yao Zi wrote:
> > > > Does the chip automatically enables WoL and loads MAC from eFuse on
> > > > power-on?
> > 
> > Yes. I pulled the power cable, kept the driver from loading and dumped
> > the registers before anything touched the chip: OOB WoL enabled, eFuse
> > address in filter 0, PMT armed for magic packet, receiver on. The
> > packet wake bit in WOL_CTRL is clear.
> 
> I've seen BIOS poke around in PHY registers before, especially if the
> BIOS has an option for WoL.

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.

I could grab some devices with U-Boot as firmware, and check against a
YT6801 addon card, which should confirm the power-on behavior.

Anyway, the approach of resetting the chip on .shutdown() to get WoL
working in S5 should have nothing to do with the power-up behavior. It
only affects whether the WoL behavior is consistent regardless of the
reason of entering S5.

>      Andrew

-- 
Thanks,
Yao Zi

Meow-mrrp-mrow, I'm a cat.


  reply	other threads:[~2026-11-17 10:27 UTC|newest]

Thread overview: 13+ 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 Wake-on-LAN from S5 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-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 [this message]
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=avwr7G83tUvZ1HP2@pie \
    --to=me@ziyao.cc \
    --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=magnusleatti@kernelriot.com \
    --cc=maxime.chevallier@bootlin.com \
    --cc=mcoquelin.stm32@gmail.com \
    --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