e1000_read_p...eg_hv_locked(9)

📦 version 7.3.1, in nixpkgs unstable

💖 e1000_read_phy_reg_hv_locked — the HV PHY register reader (kernel API manual, bestie edition) 💖

okay so first things first, the manual name is e1000_read_p...eg_hv_locked(9) — yes the title is truncated with dots, that's just how the kernel API manual rolls, we don't question it. And we're talking about a kernel API page here, so put your kernel hat on 🎀

✨ NAME ✨

e1000_read_phy_reg_hv_locked — reads an HV PHY register. that's the whole vibe. 💅

🌸 SYNOPSIS 🌸

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

like, it returns an s32, takes your hw struct, an offset, and a data pointer. simple. iconic. no notes. ⭐

🦋 ARGUMENTS 🦋

  • hw — pointer to the HW structure. your hardware bestie, the one holding all the state 🫶
  • offset — the register offset to be read. this is literally where in the PHY you're looking 👀
  • data — pointer to the read data. whatever gets read lands here, so have it ready 💖

🧚 DESCRIPTION 🧚

So basically: it reads the PHY register sitting at offset, and it stores the retrieved information into data. that's it, that's the function. 🌈

⚠️ and here's the important bit, no cap: it assumes the semaphore is already acquired. the _locked in the name is not decorative, bestie — you gotta already be holding the semaphore before you call this. don't come for this function without it 😭

👑 SEE ALSO 👑

Kernel file: ./drivers/net/ethernet/intel/e1000e/phy.c — that's where the whole squad lives 🍓

yeah that's the whole group chat, everybody's tagged 💀 but fr fr, if you're poking at HV PHY registers, one of these is gonna be your next stop.

✨ and that's a wrap, bestie ✨ this page ships out of ./drivers/net/ethernet/intel/e... and it's dated October 2026 — so yeah, future-dated kernel docs, we love to see it 🎀💜 slay, go read your registers (with the semaphore already held, obviously).

📦 where this page comes from