phy_eee_rx_clock_stop(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… phy_eee_rx_clock_stop(9) πŸ’…

okay bestie, so this is a page from the Kernel API Manual (yeah, the Kernel API Manual, we're fancy now πŸŽ€) and it's all about one tiny little function that tells your PHY whether it's allowed to ghost its receive clock. Let's get into it ✨


✨ NAME ✨

phy_eee_rx_clock_stop β€” configure PHY receive clock in LPI πŸ’€


πŸ¦‹ SYNOPSIS πŸ¦‹

int phy_eee_rx_clock_stop (struct phy_device *phydev , bool
clk_stop_enable );

literally the whole vibe in two lines, no cap πŸ’…


🌸 ARGUMENTS 🌸

  • phydev β€” the target phy_device struct, aka the PHY we're talking about 🫢
  • clk_stop_enable β€” a flag that says whether the clock can be stopped. it's giving "yes queen, power that down" or "no ma'am, keep it running" 😭

πŸ‘‘ DESCRIPTION πŸ‘‘

So what this does is configure whether the PHY can disable its receive clock during LPI mode. that's it, that's the whole job πŸ’–

and if you wanna read up on the receipts, it points you at IEEE 802.3 sections 22.2.2.2, 35.2.2.10, and 45.2.3.1.4. iykyk πŸ“š


⭐ RETURN ⭐

0 or negative error. slay when it's 0, sad girl hours when it's negative 😭


🌈 SEE ALSO 🌈

the iconic lineup, fr fr. also peep the kernel file ./drivers/net/phy/phy.c πŸ‘€


okay and for the cute sign-off: this whole thing lives in ./drivers/net/phy, the page is dated October 2026, and it's brought to you by the Kernel API Manual besties πŸ«ΆπŸ’œ periodt.

πŸ“¦ where this page comes from