phylink_rx_clk_stop_unblock(9)

🌸 NAME 🌸

phylink_rx_clk_stop_unblock — like, the function that unblocks the PHY's ability to stop the receive clock 💅 (this is the "okay bestie you can breathe again" of receive-clock-stopping permissions)

So real talk, the manual name here is phylink_rx_clk_stop_unblock(9), and it lives in the Kernel API Manual, which — yes — is exactly as iconic as it sounds 👑

---

✨ SYNOPSIS ✨

void phylink_rx_clk_stop_unblock (struct phylink *pl );

That's it. That's the whole vibe. No return value, no drama, just a void queen doing her one job 🫶

---

🎀 ARGUMENTS 🎀

• pl — a pointer to a struct phylink that came back from phylink_create 🌱 iykyk, don't just pass in some random pointer, she needs the real one

---

💖 DESCRIPTION 💖

okay so here's the tea ☕ — every single call to phylink_rx_clk_stop_block has to be balanced with a matching call to phylink_rx_clk_stop_unblock. Balanced. Like, for real. No cap.

Why? Because this is the function that restores the PHY's ability to stop the receive clock when the receive path is in EEE LPI mode ⭐ Basically phylink_rx_clk_stop_block says "nope, clock stays on," and this one says "okay bestie, you may stop it again when the situation calls for it" 🦋

Think of it as the ultimate pair — one blocks, one unblocks, and if you leave them unbalanced, that's giving unfinished business 😭

---

🌈 SEE ALSO 🌈

The main character lives right here in ./drivers/net/phy/phylink.c, and honestly the whole friend group is extensive:

• Structs & files: struct phylink(9)
• The whole phylink lore drop: phylink_set_port_modes(9), phylink_interface_max_speed(9), phylink_caps_to_link_caps(9), phylink_caps_to_linkmodes(9), phylink_limit_mac_speed(9), phylink_cap_from_speed_duplex(9), phylink_get_capabilities(9), phylink_validate_mask_caps(9), phylink_pcs_neg_mode(9), phylink_set_fixed_link(9)
• Lifecycle besties: phylink_create(9), phylink_destroy(9), phylink_expects_phy(9), phylink_connect_phy(9), phylink_of_phy_connect(9), phylink_fwnode_phy_connect(9), phylink_disconnect_phy(9), phylink_mac_change(9), phylink_pcs_change(9), phylink_start(9), phylink_stop(9)
• The sibling: phylink_rx_clk_stop_block(9) — the other half of this iconic duo 💫
• Sleep/wake era: phylink_suspend(9), phylink_prepare_resume(9), phylink_resume(9)
• ethtool zone: phylink_ethtool_get_wol(9), phylink_ethtool_set_wol(9), phylink_ethtool_ksettings_get(9), phylink_ethtool_ksettings_set(9), phylink_ethtool_nway_reset(9), phylink_ethtool_get_pauseparam(9), phylink_ethtool_set_pauseparam(9), phylink_get_eee_err(9), phylink_ethtool_get_eee(9), phylink_ethtool_set_eee(9)
• Misc icons: phylink_mii_ioctl(9), phylink_speed_down(9), phylink_speed_up(9)
• Decode girlies: phylink_decode_usxgmii_word(9), phylink_decode_usgmii_word(9)
• The c22 PCS crew: phylink_mii_c22_pcs_decode_state(9), phylink_mii_c22_pcs_get_state(9), phylink_mii_c22_pcs_encode_advertisement(9), phylink_mii_c22_pcs_config(9), phylink_mii_c22_pcs_an_restart(9)
• Replay duo: phylink_replay_link_begin(9), phylink_replay_link_end(9)

---

💀 reminder bestie: phylink_rx_clk_stop_block and phylink_rx_clk_stop_unblock are a matched set. Unbalanced calls = not the vibe. Keep the count even, periodt.

---

and that's the whole page, bestie 🧚💜 This one's brought to you from ./drivers/net/phy, dated October 2026, and it's phylink_rx_clk_stop_unblock(9) all the way down 🍓 Go balance those calls, ily, bye 😭✨