ixgbe_write_phy_reg_generic(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ixgbe_write_phy_reg_generic(9) — from the Linux Kernel API Manual, bestie

Okay so picture this: you're deep in the kernel, you need to poke a PHY register, and you want it done correctly. That's this function. It writes a value to a specified PHY register, and it does it using the SWFW lock — which is why it's the one everybody reaches for. The manpage literally says "this function is needed in most cases," and honestly? It ate. 👑

✨ NAME ✨

ixgbe_write_phy_reg_generic — writes a value to a specified PHY register using the SWFW lock. This function is needed in most cases. No cap. 🫶

🦋 SYNOPSIS 🦋

int ixgbe_write_phy_reg_generic (struct ixgbe_hw *hw , u32 reg_addr , u32 device_type , u16 phy_data );

🎀 ARGUMENTS 🎀

  • hw — pointer to the hardware structure. The main character of the whole operation, lowkey. 💖
  • reg_addr — the 32-bit PHY register you wanna write to. Tell her where to go.
  • device_type — a 5-bit device type. Tiny but mighty, five bits of pure intent. ✨
  • phy_data — the actual data being written into that PHY register. The payload, the moment, the whole point. 🌸

👑 SEE ALSO 👑

First up, the kernel file where this lives:

  • ./drivers/net/ethernet/intel/ixgbe/ixgbe_phy.c

And now the full squad — every single one of these, no skips, no cuts, periodt:

That's the whole page, bestie — every flag, every arg, every single SEE ALSO, all accounted for. 💅

Sign-off szn: this lil masterpiece comes to you from the source path ./drivers/net/ethernet/intel/i... and it's dated October 2026, still filed under ixgbe_write_phy_reg_generic(9). Slay. 🦋✨

📦 where this page comes from