phy_get_pause(9)

📦 version 7.3.1, in nixpkgs unstable

💅 phy_get_pause(9) — from the Kernel API Manual, bestie ✨

okay so picture this: it's a (9) man page, section 9, kernel API territory, and the star of the show is phy_get_pause. it's giving "small function, huge responsibility" and honestly? we're obsessed. 🎀

🌸 NAME 🌸

phy_get_pause — the girl whose whole job is resolving negotiated pause modes. that's it, that's the gig. no cap. ✨

🦋 SYNOPSIS 🦋

void phy_get_pause (struct phy_device *phydev , bool *tx_pause , bool
*rx_pause );

like, look at her. three params, returns nothing, zero drama. main character energy fr fr 💜

💖 ARGUMENTS 💖

  • phydev — the phy_device struct in question. your actual phy device, your little guy, your blorbo. 🫶
  • tx_pause — a pointer to a bool that says whether transmit pause should be enabled. yes bestie, it's a pointer — you're getting the answer back through it, not handing one in. 👑
  • rx_pause — same deal but for receive pause. pointer to a bool, tells you whether receive pause should be enabled. two bools, two pointers, one vibe check. ⭐

🌈 DESCRIPTION 🌈

so what does she actually do? phy_get_pause resolves and returns the flow control modes based on the negotiation result. that's the whole thing — the negotiation happened, and now somebody's gotta actually read the outcome and turn it into usable pause settings, and that somebody is her. 💅

and here's the part i need you to not skip: this includes checking that we are operating in full duplex mode. like, the function verifies it. if you're not in full duplex that's a whole different conversation and the function knows it. don't come for her. 😭

for the deeper lore, the manpage is like "go read linkmode_resolve_pause" — that's where the further details live. iykyk. 🧚

🔥 SEE ALSO 🔥

first up, the kernel file itself, no context needed:

Kernel file ./drivers/net/phy/phy_device.c

and then, bestie, brace yourself, because the friend group is massive — all of these are (9) entries and they all showed up to the party. not me listing every single one, but also... i absolutely am, because the manpage said so and we respect the manpage in this house 🫶

like, fifty-something functions. she knows everyone. the networking stack is her group chat. 🐛

quick reminder bestie: tx_pause and rx_pause are output pointers, so make sure they point at real bools before you call her, or that's an oopsie you did to yourself. 🙈

and that's the page!! 🍓 source livin' in ./drivers/net/phy, dated October 2026, signed off with a little 💜 and a reminder that phy_get_pause(9) ate and left no crumbs. periodt. 👑✨

📦 where this page comes from