__e1000_acc...i_reg_locked(9)

📦 version 7.3.1, in nixpkgs unstable

💅 __e1000_access_emi_reg_locked 💅

okay bestie, this is the Kernel API Manual entry for __e1000_access_emi_reg_locked (9) — yes, the manual name is literally Kernel API Manual, and this function is here to read/write an EMI register. main character energy only ✨

🌸 NAME 🌸

__e1000_access_emi_reg_locked — Read/write EMI register. that's it, that's the gig, periodt 💖

✨ SYNOPSIS ✨

bestie, here's the exact signature, character for character, no cap:

s32 __e1000_access_emi_reg_locked (struct e1000_hw *hw , u16 address ,
u16 *data , bool read );

💖 ARGUMENTS 💖

  • hw — pointer to the HW structure 🫶
  • address — EMI address to program 📍
  • data — pointer to value to read/write from/to the EMI address 🎀
  • read — boolean flag to indicate read or write 🔥

🦋 DESCRIPTION 🦋

okay so this helper function assumes the SW/FW/HW Semaphore is already acquired. that's the whole vibe check. it assumes the semaphore is already held when you call it — so handle your locking business first, bestie 💅

👑 SEE ALSO 👑

the extended ich8lan/e1000e cinematic universe, fr fr:

and that's the page, bestie 🫶 the footer situation is source/version ./drivers/net/ethernet/intel/e... and date October 2026, attached to __e1000_acc...i_reg_locked(9) — mwah 💋✨

📦 where this page comes from