igb_write_phy_reg_igp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… igb_write_phy_reg_igp(9) β€” the Kernel API Manual glow-up ✨

okay so bestie, welcome to the igb_write_phy_reg_igp page from the Kernel API Manual πŸŽ€ this one's short and sweet and honestly kind of iconic for it.


🌸 NAME 🌸

igb_write_phy_reg_igp β€” write an igp PHY register πŸ’–


✨ SYNOPSIS ✨

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

like, that's the whole signature. no notes. she's tidy 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • hw β€” pointer to the HW structure πŸ’… that's your hardware context right there, the main character of this whole operation
  • offset β€” register offset to write to ⭐ literally which register you're sliding into
  • data β€” data to write at register offset 🌸 the actual payload, the moment, the reason we're all here

🌈 DESCRIPTION 🌈

okay so here's the vibe: she acquires the semaphore first β€” but only if necessary, no cap πŸ™ˆ β€” and then she writes the data to the PHY register at the offset. super straightforward, does exactly what it says on the tin πŸ’œ

and then, bestie, listen: she releases any acquired semaphores before exiting πŸ‘‘ not me being obsessed with proper cleanup. she does NOT leave a semaphore held on her way out. that's called manners and she has them fr fr ✨


πŸŽ€ SEE ALSO πŸŽ€

like yes that's a lot of siblings but they're all family πŸ’€ go read them too iykyk πŸ”₯


okay that's the page!! mwah πŸ’‹ this one lives in ./drivers/net/ethernet/intel/igb, dated October 2026, and the whole thing is served up by that manpage source, so that's your sign-off bestie β€” go write some registers responsibly πŸ§šβ€β™€οΈπŸ¦‹β­

πŸ“¦ where this page comes from