genphy_setup_forced(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… genphy_setup_forced(9) β€” the Kernel API Manual glow-up

okay bestie, so this page lives in the Kernel API Manual section 9, and it's all about one tiny function that just sets the vibe of your PHY β€” forcibly πŸ’…


🌸 NAME

genphy_setup_forced β€” literally configures/forces speed/duplex from @phydev


✨ SYNOPSIS

int genphy_setup_forced (struct phy_device *phydev );

πŸŽ€ ARGUMENTS

  • phydev β€” the target phy_device struct, aka the PHY you're about to give a makeover 🫢

πŸ’– DESCRIPTION

So here's the tea: genphy_setup_forced configures MII_BMCR to force speed/duplex to whatever values are already sitting in phydev. Like, no negotiation, no asking, just β€” this is the look, we're committing to it πŸ‘‘

And hmm, it assumes that the values are valid. That's the whole disclaimer, bestie. It is not out here doing vibe checks on your numbers. Please see phy_sanitize_settings if you want someone to actually verify things first 🧚

⚠️ Fr fr, if the values in phydev aren't legit, this function is not going to catch that for you. Sanitize first, okay? πŸ™ˆ

πŸ¦‹ SEE ALSO

Kernel file ./drivers/net/phy/phy_device.c and honestly a whole friend group of functions:


and that's the whole page, periodt ✨

This little icon comes to you from ./drivers/net/phy, stamped October 2026 β€” genphy_setup_forced(9), slaying since forever πŸŽ€πŸ’œ

πŸ“¦ where this page comes from