e1000e_writ...g_igp_locked(9)

📦 version 7.3.1, in nixpkgs unstable

💅 e1000e_write_phy_reg_igp_locked(9) 💅

okay so real talk, this page lives in the Kernel API Manual and the header renders it all squished as e1000e_writ...g_igp_locked(9) (yes the title got truncated, that's just the man page being dramatic) — the actual star of the show is e1000e_write_phy_reg_igp_locked. she writes one (1) PHY register. that's the whole vibe. ✨

🎀 NAME 🎀

e1000e_write_phy_reg_igp_locked — write igp PHY register. that's it, that's the function, and honestly she ate. 💖

✨ SYNOPSIS ✨

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

like, she takes three things and gives you back an s32. no cap. 🫶

🌸 ARGUMENTS 🌸

  • hw — pointer to the HW structure. your hardware bestie, the whole context, the main character of every e1000e function fr fr.
  • offset — register offset to write to. which slot are we putting the data in, bestie? 🎯
  • data — data to write at register offset. the actual payload, the moment, the reason we're all here. 💌

🦋 DESCRIPTION 🦋

Writes the data to the PHY register at the offset. simple, clean, iconic. 🌟

⚠️ heads up though — this one assumes the semaphore is already acquired. she does not grab it for you, she just walks in and does the write. so if you didn't lock first, that's on you, and the vibes will be immaculate in the worst way. 🔒💀

🌈 SEE ALSO 🌈

the kernel file, right here: ./drivers/net/ethernet/intel/e1000e/phy.c — that's the source, the home base, the origin story. 🏠

and like... the entire extended friend group, no exaggeration. every single one of these:

like I said. the whole group chat. 🫶💀

and that's the page, bestie! source/version is ./drivers/net/ethernet/intel/e..., dated October 2026, and it's all filed under e1000e_writ...g_igp_locked(9) in the Kernel API Manual. go forth and write your registers (after you lock, obviously 😭). mwah! 💋🎀✨

📦 where this page comes from