t3_wait_op_done_val(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ t3_wait_op_done_val(9) πŸŽ€

🌸 NAME 🌸

t3_wait_op_done_val β€” wait until an operation is completed. Yes bestie, that’s the whole NAME vibe, and this page is straight outta the Kernel API Manual πŸ’–.

✨ SYNOPSIS ✨

int t3_wait_op_done_val (struct adapter *adapter , int reg , u32 mask ,
       int polarity , int attempts , int delay , u32 *valp );

πŸŽ€ ARGUMENTS πŸŽ€

Okay so here’s the group chat, argument by argument:

  • adapter β€” the adapter performing the operation.
  • reg β€” the register to check for completion.
  • mask β€” a single-bit field within reg that indicates completion.
  • polarity β€” the value of the field when the operation is completed.
  • attempts β€” number of check iterations.
  • delay β€” delay in usecs between iterations.
  • valp β€” where to store the value of the register at completion time.

πŸ’… DESCRIPTION πŸ’…

Okay bestie, the vibe check: wait until an operation is completed by checking a bit in a register up to attempts times. If valp is not NULL, the value of the register at the time it indicated completion is stored there. Returns 0 if the operation completes and -EAGAIN otherwise. No cap, that’s literally the behavior. πŸ”₯

πŸ‘€ SEE ALSO πŸ‘€

Kernel file: ./drivers/net/ethernet/chelsio/cxgb3/t3_hw.c β€” and then the whole squad of related references, periodt:


🫢 That’s a wrap, bestie! Source/version: ./drivers/net/ethernet/chelsio... Β· date: October 2026. Go wait on that op and slay πŸ’…βœ¨
πŸ“¦ where this page comes from