ti_abb_wait_txdone(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ti_abb_wait_txdone πŸ’–

okay so bestie, welcome to the kernel API manual for ti_abb_wait_txdone, a function that literally just waits for the ABB tranxdone event πŸŽ€ no cap, that's the whole vibe. It's living its best life over in the kernel API manual, and today we're gonna understand it together 🫢


✨ NAME ✨

ti_abb_wait_txdone β€” waits for ABB tranxdone event πŸ’…

Like, it waits. For the ABB. Specifically for the tranxdone event. Iconic behavior honestly πŸ‘‘


🌸 SYNOPSIS 🌸

int ti_abb_wait_txdone (struct device *dev , struct ti_abb *abb );

That's the whole signature, and yes it returns an int, and yes it takes those two args β€” we're getting into them right now πŸ¦‹


πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” device
  • abb β€” pointer to the abb instance

that's it. that's the args. one's the device, one's a pointer to the abb instance, and if you mixed them up the compiler would absolutely read you for filth 😭


⭐ RETURN ⭐

0 on success or -ETIMEDOUT if the event is not cleared on time.

so if everything's chill you get 0 β€” but if that event is still hanging around past the deadline, you get -ETIMEDOUT and honestly that's the vibe check failing πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./drivers/regulator/ti-abb-regulator.c, plus the whole friend group:

go read ti_abb_check_txdone(9) and ti_abb_clear_txdone(9) next bestie, they're literally the sibling functions to this one and they ate πŸ”₯ iykyk


and that's the page! 🌈 this iconic little number lives in ./drivers/regulator, dated October 2026, and it's part of the Kernel API Manual β€” mwah, go wait on that txdone event, you're doing amazing sweetie πŸ’œπŸŽ€βœ¨

πŸ“¦ where this page comes from