e1000e_write_phy_reg_m88(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME

e1000e_write_phy_reg_m88 β€” write that m88 PHY register, bestie ✨

So this whole page is from the Kernel API Manual, and it's all about one little function that pokes a value into a PHY register. Short king, honestly. πŸ‘‘


✨ SYNOPSIS

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

That's the whole vibe. It hands back an s32, and it takes three things. Keep scrolling for the deets πŸ’…


πŸŽ€ ARGUMENTS

  • hw β€” pointer to the HW structure 🫢 like, the hardware context, the whole situation
  • offset β€” the register offset you're writing to, i.e. where in the register map we're going
  • data β€” the actual data you want to write at that register offset, the payload, the moment πŸ’«

πŸ¦‹ DESCRIPTION

Okay so here's the tea β˜• β€” this function acquires the semaphore, if necessary, and then writes the data to the PHY register at the offset. Simple, iconic, no notes.

And the last part is genuinely important, so don't skip it: it releases any acquired semaphores before exiting. πŸšͺ✨ Like, always give the lock back. No cap.

Lowkey the semaphore bookkeeping is the whole personality of this function. Acquire if needed, release before you dip. Periodt. πŸ’…

🌈 SEE ALSO

First up, the kernel file this bad girl lives in:

  • Kernel file ./drivers/net/ethernet/intel/e1000e/phy.c

And now the full squad, the whole friend group, every single one of them, no girl left behind πŸ’–:


That's the whole page, bestie, you ate that πŸ’…βœ¨

Oh and before I forget β€” the footer vibes: this one's sourced from ./drivers/net/ethernet/intel/e... and dated October 2026, and it's still serving e1000e_write_phy_reg_m88(9) energy. Slay. πŸŽ€πŸ’–

πŸ“¦ where this page comes from