ixgbe_read_phy_reg_mdi(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ ixgbe_read_phy_reg_mdi(9) ✨

Okay so welcome to the Kernel API Manual, bestie 🫢 β€” today we're looking at ixgbe_read_phy_reg_mdi, which is literally just a function that reads a PHY register. That's it. That's the whole vibe. πŸ’…


🌸 NAME 🌸

ixgbe_read_phy_reg_mdi β€” read PHY register πŸ‘‘


πŸŽ€ SYNOPSIS πŸŽ€

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

πŸ¦‹ ARGUMENTS πŸ¦‹

  • hw β€” pointer to hardware structure. it's giving "here's the hardware, go off" ✨
  • reg_addr β€” 32 bit address of PHY register to read πŸ”
  • device_type β€” 5 bit device type. yes, five bits, tiny icon behavior πŸ’…
  • phy_data β€” Pointer to read data from PHY register. the data lands here πŸ“

πŸ’œ DESCRIPTION πŸ’œ

It reads a value from a specified PHY register β€” and the way it does it is without the SWFW lock. no cap, that's the whole description. πŸ“–βœ¨

Heads up bestie: no SWFW lock means no software/firmware locking around this read. that's the documented behavior, so keep that in mind before you go wild πŸ™ˆ

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/net/ethernet/intel/ixgbe/ixgbe_phy.c β€” that's where the whole friend group lives 🧚

Like, that's the entire friend group and they ALL showed up to the function's birthday party πŸŽ‰πŸ‘―β€β™€οΈ


mwah πŸ’‹ this page came from ./drivers/net/ethernet/intel/i... and it's dated October 2026, so mark your calendars, bestie β€” see you then 🌈⭐

πŸ“¦ where this page comes from