__e1000_read_phy_reg_hv(9)

📦 version 7.3.1, in nixpkgs unstable

💖 __e1000_read_phy_reg_hv — the kernel API manual, bestie edition 💖

Okay so first things first, the title on this one is __e1000_read_phy_reg_hv(9) and it lives in the Kernel API Manual, which is literally the group chat where all the kernel functions hang out. And yes, there are two leading underscores — that's not a typo, that's main character energy. 🎀

✨ NAME ✨

__e1000_read_phy_reg_hv — read an HV PHY register 🦋

Like, that's it. That's the whole job. It reads a PHY register, and it's the HV flavour specifically. No cap.

🌸 SYNOPSIS 🌸

s32 __e1000_read_phy_reg_hv (struct e1000_hw *hw , u32 offset , u16
*data , bool locked , bool page_set );

Returns an s32 (yes, a signed 32-bit int, she's got range), takes a pointer to the HW structure, an offset, a pointer to where the data goes, and two bools that control whether the semaphore is already held and whether the page is already set up. Five arguments, all of them important, none of them optional. Slay. 💅

👑 ARGUMENTS 👑

  • hw — pointer to the HW structure. Like, the whole hardware vibe lives in here. 🫶
  • offset — the register offset you wanna read. Exactly which register, pls be specific. 🔥
  • data — pointer to the read data. This is where the answer gets dropped off. It's an out-param and she's the star of the show. ⭐
  • locked — says whether the semaphore has already been acquired or not. Basically: "did somebody already grab the lock, or do I need to?" 🙈
  • page_set — BM_WUC_PAGE is already set and access is enabled. So like, the page situation is handled, don't worry about it. 💜

🧚 DESCRIPTION 🧚

So here's the tea, bestie. 💖 This function acquires the semaphore if necessary — that "if necessary" is huge, it's literally the whole reason the locked argument exists — and then reads the PHY register at offset and stores the retrieved info in data.

And then it releases any semaphore it acquired before exiting. Every time. No leaking locks, no messy exits, she's responsible like that. Your fave could never. ✨

Lowkey important: if it grabbed a semaphore, it gives it back before it leaves. That's the contract. Don't be the function that forgets, okay? 😭

🌈 SEE ALSO 🌈

And now, the moment you've all been waiting for: the entire extended friend group. She knows everyone, fr fr. 💀

First up, the source file this whole situation lives in:

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

Then, the whole (9) crew, alphabetically-ish, all seventy-three of them:

See what I mean? Iconic. Networking function royalty, the whole lot of them. 🌟

🎀 sign-off 🎀

This little masterpiece comes to you from the source file ./drivers/net/ethernet/intel/e... (it got cut off in the footer, don't come for her, she was running out of room 😭) and it's dated October 2026. The page itself is __e1000_read_phy_reg_hv(9), in case you forgot already, which, fair. 🍓

Anyway bestie, go read those HV PHY registers. Responsibly. With the semaphore. 💜✨💅

📦 where this page comes from