phy_write_paged(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– phy_write_paged(9) πŸ’–

okay bestie, welcome to the Kernel API Manual entry for phy_write_paged(9) β€” the lowkey convenience function for writing a paged register. It’s giving β€œone little write, but on a page,” and we’re gonna get you comfy with it. ✨


🌸 NAME 🌸

phy_write_paged β€” convenience function for writing a paged register. That’s the whole name-and-one-liner combo, and yes, it ate. πŸ’…

πŸ¦‹ SYNOPSIS πŸ¦‹

int phy_write_paged (struct phy_device *phydev , int page , u32 regnum ,
u16 val );

πŸ’… ARGUMENTS πŸ’…

  • phydev β€” a pointer to a struct phy_device. Like, this is the PHY device bestie we’re talking about. 🫢
  • page β€” the page for the phy. Yep, that page. πŸ‘‘
  • regnum β€” register number. The number of the register, periodt. πŸ”₯
  • val β€” value to write. The actual value going in. ⭐

πŸ“ DESCRIPTION πŸ“

The description is short and iconic: Same rules as for phy_write.

That’s it. That’s the whole vibe check on this page β€” if you know phy_write, you already know the rules here. Go check phy_write for the details, bestie. No cap. πŸ’œ

🌈 SEE ALSO 🌈

Kernel file ./drivers/net/phy/phy-core.c β€” and here’s the whole friend group of related functions, all gathered so you can go click around in the source:


Signed, sealed, and slayed by the source tree at ./drivers/net/phy, with the manual dated October 2026 β€” mwah πŸ’‹πŸŽ€

πŸ“¦ where this page comes from