__e1000e_write_phy_reg_igp(9)

📦 version 7.3.1, in nixpkgs unstable

💅 __e1000e_write_phy_reg_igp — from the Kernel API Manual, bestie

okay so we're diving into the kernel, specifically the e1000e driver, and this function is literally the one that writes to an igp PHY register. lowkey iconic, highkey niche. let's get into it 🫶

✨ NAME ✨

__e1000e_write_phy_reg_igp — writes to an igp PHY register. that's the whole vibe. no cap. 🎀

🦋 SYNOPSIS 🦋

s32 __e1000e_write_phy_reg_igp (struct e1000_hw *hw , u32 offset , u16 data , bool locked );

it gives you back an s32, so like… check your return value, queen. 🌸

💖 ARGUMENTS 💖

  • hw — pointer to the HW structure. it's giving "here's the hardware, do something with it" energy 👑
  • offset — the register offset you wanna write to. pick your spot ✨
  • data — the actual data getting written at that register offset. this is the payload, the main character of the operation 🎀
  • locked — a bool that tells you whether the semaphore has already been acquired or not. like, is the door already held open or are we grabbing the handle ourselves 🙈

🌈 DESCRIPTION 🌈

so here's the tea ☕: this function acquires the semaphore if necessary, then writes the data to the PHY register at the offset. and then — and this is the responsible part — it releases any acquired semaphores before exiting. clean up after yourself, bestie, that's the rule 💅

literally: lock it up if you gotta, do the write, unlock what you locked, leave. periodt.

heads up 🫶: whether it grabs the semaphore depends on that locked argument — if it's already been acquired, it won't re-acquire. that's the whole point of passing it in.

🔥 SEE ALSO 🔥

the kernel file lives right here: ./drivers/net/ethernet/intel/e1000e/phy.c 📁

and now the friend group — every single one of these, no skips, fr fr:

that's the whole page, bestie 💜 source came from ./drivers/net/ethernet/intel/e... (the path gets truncated in the footer, we don't make the rules 😭), and it's stamped October 2026 — so yeah, future-dated and thriving 🦋✨ ily, go write some registers responsibly! 🎀

📦 where this page comes from