e1000_disabl...eg_access_bm(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay bestie, we're in the Kernel API Manual and this page is e1000_disabl...eg_access_bm(9) — yes the header shows the name twice, but we're folding it in right here instead of copying that line 💅. The function is e1000_disable_phy_wakeup_reg_access_bm, and its whole job is to disable access to BM wakeup regs. Periodt.

✨ SYNOPSIS ✨

s32 e1000_disable_phy_wakeup_reg_access_bm (struct e1000_hw *hw , u16
*phy_reg );

🎀 ARGUMENTS 🎀

  • hw — pointer to the HW structure. iconic little handle, no notes.
  • phy_reg — pointer to original contents of BM_WUC_ENABLE_REG. this is the "before" snapshot, keep it safe 🫶.

🦋 DESCRIPTION 🦋

The vibe here is simple: restore BM_WUC_ENABLE_REG to its original value. That's the move. That's the slay ✨.

Important vibe check: this assumes semaphore already acquired and *phy_reg is the contents of the BM_WUC_ENABLE_REG before register(s) on BM_WUC_PAGE were accessed by caller. no cap, those assumptions are doing a lot of work 😭.

💖 SEE ALSO 💖

Kernel file: ./drivers/net/ethernet/intel/e1000e/phy.c

okay bestie, here's the full SEE ALSO friend group — same names, no edits, no missing members:

cute little sign-off tea ☕: the footer source/version is ./drivers/net/ethernet/intel/e..., the date is October 2026, and the manual name is e1000_disabl...eg_access_bm(9). byeee, go restore that register responsibly 💜🫶✨

📦 where this page comes from