phy_read_paged(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– phy_read_paged(9) β€” the kernel API manual, but make it make sense πŸ’–

okay so this is a page from the kernel API manual (section 9, the function-page girlies ✨) and honestly? it's short, it's sweet, and it does exactly one thing. let's get into it 🫢


🌸 NAME 🌸

phy_read_paged β€” the convenience function for reading a paged register. that's it, that's the whole vibe. it's giving "shortcut so you don't have to do the page dance yourself" πŸ’…


✨ SYNOPSIS ✨

int phy_read_paged (struct phy_device *phydev , int page , u32 regnum );

like, look at her. three args, returns an int, no notes. iconic πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • phydev β€” a pointer to a struct phy_device. your phy bestie. you gotta hand her over πŸ’–
  • page β€” the page for the phy. yeah. the page. for the phy. that's the whole description, i don't make the rules πŸ¦‹
  • regnum β€” register number, aka which register you're trying to peek at πŸ”

🧚 DESCRIPTION 🧚

Same rules as for phy_read. periodt. that's genuinely all it says β€” so if you know how phy_read behaves, you already know how this one behaves, no cap πŸ’€βœ¨


🌈 SEE ALSO 🌈

the kernel file ./drivers/net/phy/phy-core.c is where all this lives, and here's the whole friend group β€” every single one of them, i'm not skipping a single bestie 😀:

like, that's a full group chat right there. the paged-register crew, the mmd crew, the modify crew β€” all mutually obsessed πŸ«ΆπŸ’œ


ngl bestie, this one's a "read the docs for phy_read first" situation. this page literally tells you to. respect the lore πŸ™ˆ

and that's the page!! sign-off time: this lives in ./drivers/net/phy, it's dated October 2026, and it's from the kernel API manual section 9. mwah, go read a register, slay πŸ’‹πŸ’–πŸŒΈ

πŸ“¦ where this page comes from