e1000e_read_kmrn_reg_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ e1000e_read_kmrn_reg_locked β€” Read kumeran register

okay so this is a page straight out of the Kernel API Manual (section 9, the kernel-functions one, iykyk) β€” and it's about reading a single kumeran register. tiny function, big main character energy. let's get into it πŸ’…


✨ SYNOPSIS ✨

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

that's the whole vibe. three args, one return, no cap. 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • hw β€” pointer to the HW structure πŸ’– this is the hardware context bestie, everything hangs off it.
  • offset β€” register offset to be read 🌸 literally which register you're going for.
  • data β€” pointer to the read data ⭐ the goods get written back through here.

πŸ”₯ DESCRIPTION πŸ”₯

Reads the PHY register at offset using the kumeran interface. The information retrieved is stored in data. πŸ‘‘

and the big one, the thing you cannot skip:

Assumes semaphore already acquired. 🚨 like, the _locked in the name is not decorative bestie, it's literally telling you the locking is already handled and it's on YOU to have done it. read the room.

the function hands back a s32, so yeah, check your return value. slay. ✨


πŸ’œ SEE ALSO πŸ’œ

Kernel file ./drivers/net/ethernet/intel/e1000e/phy.c β€” that's the home base 🏠

then the whole extended friend group, in order, no skipping, no cutting corners (there are a LOT of them and we love that for us):

like I said. the whole group chat. 😭🫢


okay that's the page!! lil sign-off before you go: this one lives over in ./drivers/net/ethernet/intel/e... and it's dated October 2026. go read some kumeran registers bestie, and please acquire that semaphore first. πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from