phy_trigger_machine(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… phy_trigger_machine(9) β€” like, the Kernel API Manual page, bestie ✨

okay so picture this: you're deep in the Kernel API Manual, poking at the PHY layer, and you just need the state machine to go β€” right now, no waiting, no "soon", no queue-and-chill. That's this function. It's giving main character energy for exactly one job πŸŽ€


🌸 NAME 🌸

phy_trigger_machine β€” trigger the state machine to run now ⚑

Literally that's it. It pokes the state machine and goes "bestie, run. now. periodt."


πŸ¦‹ SYNOPSIS πŸ¦‹

void phy_trigger_machine (struct phy_device *phydev );

Returns nothing (void), takes one thing. That's the whole vibe check 🫢


πŸ’– ARGUMENTS πŸ’–

  • phydev β€” the struct phy_device struct. Yeah. That's the whole description. It's the phy_device struct, and honestly? She said what she said πŸ™ˆ

πŸ”₯ SEE ALSO πŸ”₯

Like, this function does not exist in a vacuum, okay? The whole friend group lives in the kernel file ./drivers/net/phy/phy.c and here's every single one of them β€” no cap, every last one, don't @ me πŸ’€

ngl go check out phy_state_machine(9) next, she's the one actually doing the running β€” this page is just the "hey!! wake up!!" text πŸ’…

okay that's the whole page, you ate that πŸ“ and for the sign-off: this little icon lives in ./drivers/net/phy, dated October 2026, and she's filed under phy_trigger_machine(9) β€” slay, bye πŸ‘‘βœ¨

πŸ“¦ where this page comes from