From: Andrew Lunn <andrew@lunn.ch>
To: Birger Koblitz <mail@birger-koblitz.de>
Cc: Emir Beganovic <beganovic.emir@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Russell King <linux@armlinux.org.uk>,
Heiner Kallweit <hkallweit1@gmail.com>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
Eric Dumazet <edumazet@kernel.org>,
Jianhui Xu <neuromoments@gmail.com>,
Nicolai Buchwitz <nb@tipi-net.de>,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev
Subject: Re: [PATCH net-next v19 00/13] ax88179_178a: Add support for AX88179A-based chips
Date: Fri, 30 Oct 2026 17:47:43 +0100 [thread overview]
Message-ID: <e7603c1d-4b1a-48be-a9da-9f9cf888cff6@lunn.ch> (raw)
In-Reply-To: <2a66e94c-0fd0-4c90-bc1c-9e5699f80737@birger-koblitz.de>
> > - After a WoL wake the link goes down and up twice within about 2.5 s,
> > where a normal resume shows a single link up. It comes back fine
> > either way.
> I see this, too. It is not triggered in any way by the host or the link
> partner, I checked. It appears that this is due to the firmware on the
> device trying to optimize the link settings further, the out-of tree ASIX
> driver displays the same behaviour, although it works very differently.
phylink/phylib might be playing a role in this.
It takes about 1 Watt more energy to have a 1G link vs a 10Mbps link,
even when there is no traffic. So during suspend with WoL enabled,
phylib tries to reduce the link speed to the lowest common speed,
hopefully 10Mbps, by only advertising that one link speed. On resume
it goes back to advertising the full link capabilities.
So one of the down/up you are seeing might be this.
Andrew
prev parent reply other threads:[~2026-10-30 16:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 4:54 Birger Koblitz
2026-10-10 4:54 ` [PATCH net-next v19 01/13] phylink: Add phylink_mac_interrupt Birger Koblitz
[not found] ` <sashiko-outbox-167008@kernel.org>
2026-10-11 5:32 ` Birger Koblitz
2026-10-20 0:18 ` Jakub Kicinski
2026-10-20 3:50 ` Birger Koblitz
2026-10-10 4:54 ` [PATCH net-next v19 02/13] phylib: Add support for PHYs with broken forced mode Birger Koblitz
2026-10-10 4:54 ` [PATCH net-next v19 03/13] ax88179_178a: Split driver into library and device specific code Birger Koblitz
2026-10-10 4:54 ` [PATCH net-next v19 04/13] ax88179_178a: Add HW support for AX179A-based chips Birger Koblitz
2026-10-10 4:54 ` [PATCH net-next v19 05/13] ax88179_178a: Add EEE configuration support for AX88179A MACs Birger Koblitz
2026-10-10 4:54 ` [PATCH net-next v19 06/13] ax88179_178a: Add EEE configuration support for AX88179A PHYs Birger Koblitz
2026-10-10 4:54 ` [PATCH net-next v19 07/13] ax88179_178a: Add VLAN offload support for AX88179A Birger Koblitz
2026-10-10 4:54 ` [PATCH net-next v19 08/13] ax88179_178a: Add AX179A/AX279 multicast configuration Birger Koblitz
2026-10-10 4:54 ` [PATCH net-next v19 09/13] ax88179_178a: Add Suspend/resume support for AX88179A/772D/279 Birger Koblitz
2026-10-10 4:54 ` [PATCH net-next v19 10/13] ax88179_178a: Add ethtool get_drvinfo Birger Koblitz
2026-10-10 4:54 ` [PATCH net-next v19 11/13] ax88179_178a: Update driver name and information Birger Koblitz
2026-10-10 4:54 ` [PATCH net-next v19 12/13] ax88179_178a: Add support for AX88179A/772D/279 EEPROM access Birger Koblitz
2026-10-10 4:54 ` [PATCH net-next v19 13/13] ax88796b: Add support for AX88772D, AX88179A and AX88279 Birger Koblitz
2026-10-10 6:20 ` [PATCH v19 0/13] ax88179_178a: Add support for AX88179A-based chips Jianhui Xu
2026-10-10 7:42 ` Birger Koblitz
2026-10-29 0:58 ` [PATCH net-next v19 00/13] " Emir Beganovic
2026-10-30 15:42 ` Birger Koblitz
2026-10-30 16:47 ` Andrew Lunn [this message]
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=e7603c1d-4b1a-48be-a9da-9f9cf888cff6@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=beganovic.emir@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=kernel@xen0n.name \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=loongarch@lists.linux.dev \
--cc=mail@birger-koblitz.de \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=neuromoments@gmail.com \
--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®