e1000e_write...n_reg_locked(9)

📦 version 7.3.1, in nixpkgs unstable

💅 e1000e_write...n_reg_locked(9) — Kernel API Manual ✨

okay so bestie, welcome to the Kernel API Manual, and today's main character is e1000e_write_kmrn_reg_locked 🎀 like yes, the locked one, we love a responsible queen who shows up with the semaphore already handled 🫶

✨ NAME ✨

e1000e_write_kmrn_reg_locked — Write kumeran register 💖

🌸 SYNOPSIS 🌸

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

🎀 ARGUMENTS 🎀

  • hw — pointer to the HW structure. it's giving "here's the hardware bestie, go off" ✨
  • offset — register offset to write to. the exact spot you're aiming at, no cap 📍
  • data — data to write at register offset. the actual payload, the moment, the ~content~ 💅

🦋 DESCRIPTION 🦋

So what this icon does: it writes the data to the PHY register at the offset, using the kumeran interface. literally that's the whole vibe.

⚠️ and this part matters, bestie: it assumes semaphore already acquired. like, do NOT come here without it. the locking is your job, this function is not doing it for you — it said "you handle the semaphore, i handle the write" and honestly? boundaries. we respect them 🙈

🌈 SEE ALSO 🌈

Kernel file: ./drivers/net/ethernet/intel/e1000e/phy.c — that's the home base 🏠

and now the full friend group, the whole group chat, everybody in the PHY-verse 👑:

and that's the whole squad, no one left out, we don't do exclusion here 💜

mwah 💋 this page came from ./drivers/net/ethernet/intel/e... and it's dated October 2026 — screenshot it, frame it, it's iconic ✨🎀

📦 where this page comes from