e1000_read_phy_reg_page_hv(9)

📦 version 7.3.1, in nixpkgs unstable

💖 e1000_read_phy_reg_page_hv(9) 💖

okay so bestie, welcome to the Kernel API Manual ✨ — today's main character is e1000_read_phy_reg_page_hv, and honestly? she's a tiny little function with a very specific job and she does it. no notes. 🎀

🌸 NAME 🌸

e1000_read_phy_reg_page_hv — Read HV PHY register 💅

✨ SYNOPSIS ✨

s32 e1000_read_phy_reg_page_hv (struct e1000_hw *hw , u32 offset , u16
*data );

like yes that's the whole signature, she's not trying to be mysterious 🦋

🫶 ARGUMENTS 🫶

  • hw — pointer to the HW structure ✨ (the hardware vibe holder, she needs it)
  • offset — register offset to write to
  • data — data to write at register offset
ngl the labels literally say "write to" on a read function and I'm not gonna gaslight you about it — that's what the page says, word for word, and I'm just the messenger 💀🙈

👑 DESCRIPTION 👑

Reads the PHY register at offset and stores the retrieved information in data. 📥

Assumes semaphore already acquired and page already set. no cap — those two things are on you, boo. she's not doing them for you, she's just doing the read. periodt 💅

🌈 SEE ALSO 🌈

the kernel file in question, iconic: ./drivers/net/ethernet/intel/e1000e/phy.c 📁

and now, the guest list — every single one of these besties made the cut, we're not doing anyone dirty 🎀

she's giving "small function, big ecosystem" — and honestly the way she's referenced by like everyone in phy.c? ate. 🔥

sign-off time 💜 this little gem lives at ./drivers/net/ethernet/intel/e..., dated October 2026, and the page itself is e1000_read_phy_reg_page_hv(9) — mwah, go read some PHY registers bestie, you got this 💅✨🍓

📦 where this page comes from