t1_wait_op_done(9)

💅 t1_wait_op_done(9) — the "are we there yet" of kernel API manual pages ✨

okay so this is t1_wait_op_done(9) from the Kernel API Manual bestie, and it's literally just the politest way to ask a register "u done yet??" over and over 🎀

✨ NAME ✨

t1_wait_op_done — wait until an operation is completed 🫶

🌸 SYNOPSIS 🌸

int t1_wait_op_done (adapter_t *adapter , int reg , u32 mask , int
polarity , int attempts , int delay );

🦋 ARGUMENTS 🦋

• adapter — the adapter performing the operation, it's giving main character energy 👑
• reg — the register to check for completion, this is the spot we keep staring at 👀
• mask — a single-bit field within reg that indicates completion, no cap, literally just one bit 🔥
• polarity — the value of the field when the operation is completed, like the vibe check that finally passes ✅
• attempts — number of check iterations, aka how many times we're willing to ask 😭
• delay — delay in usecs between iterations, lil breather between asks 🧚

💜 DESCRIPTION 💜

Wait until an operation is completed by checking a bit in a register up to attempts times. Returns 0 if the operation completes and 1 otherwise. periodt 💅

ngl the whole thing is a loop with manners — check the bit, wait delay usecs, check again, up to attempts times, then report back with a 0 (slay, it's done) or a 1 (it did not, in fact, slay) 🙈

⭐ SEE ALSO ⭐

Kernel file ./drivers/net/ethernet/chelsio/cxgb/subr.c — go read the source bestie, iykyk 🌈

and that's the page!! 🌸 brought to you by the source ./drivers/net/ethernet/chelsio... dated October 2026, mwah, drink water, and may all ur bits flip in time 💖💅✨