phylink_suspend(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so this is phylink_suspend, straight out of the Kernel API Manual, and it's literally the "your network device is going night-night" handler. bestie, it's a whole vibe check for suspend events πŸ’…


✨ NAME ✨

phylink_suspend β€” handle a network device suspend event πŸŽ€


🌸 SYNOPSIS 🌸

void phylink_suspend (struct phylink *pl , bool mac_wol );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • pl β€” a pointer to a struct phylink that came back from phylink_create. that's your lil phylink handle, your main character 🫢
  • mac_wol β€” true if the MAC needs to keep receiving packets for Wake-on-Lan. like, the MAC is staying up for WOL purposes, okurrr πŸ”₯

πŸ’– DESCRIPTION πŸ’–

Handle a network device suspend event. and ngl, there are several cases, so let's break it down like a group chat πŸ’¬

  • If Wake-on-Lan is not active, we can bring down the link between the MAC and PHY by calling phylink_stop. easy, link goes bye-bye 😴
  • If Wake-on-Lan is active, and it's being handled only by the PHY, we can also bring down the link between the MAC and PHY. slay, the PHY's got it, MAC can chill πŸ’…
  • If Wake-on-Lan is active, but it's being handled by the MAC, then the MAC still needs to receive packets β€” so we can not bring the link down. nope, absolutely not, the MAC is still on duty πŸ™ˆ

⚠️ NOTE ⚠️

when phylink managed Wake-on-Lan is in use, mac_wol is ignored. periodt. (struct phylink_mac_ops.mac_set_wol populated.) πŸ’€


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/net/phy/phylink.c β€” and like, the whole phylink cinematic universe, fr fr:


okay that's the whole page, you ate that πŸ“ this lil manpage lives in ./drivers/net/phy and it's dated October 2026 β€” yes, future queen behavior πŸ‘‘βœ¨ mwah, go read the source πŸ’œ

πŸ“¦ where this page comes from