k3rtc_fence(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

NAME πŸ’–

k3rtc_fence(9) β€” direct from the Kernel API Manual β€” is the function that makes sure a register sync actually happened between the two domains. That’s the whole assignment, bestie: sync check, no cap ✨

SYNOPSIS ✨

int k3rtc_fence (struct ti_k3_rtc *priv );

ARGUMENTS πŸŽ€

  • priv β€” pointer to priv data. That’s it, that’s the argument, she’s just a pointer to the priv data πŸ’…

RETURN πŸ¦‹

  • 0 if the sync took place. Slay.
  • Otherwise it returns -ETIMEDOUT. So if the sync didn’t happen, you get that timeout-flavored error 😭

SEE ALSO 🌸

  • Kernel file ./drivers/rtc/rtc-ti-k3.c
  • struct ti_k3_rtc(9)

Cute little sign-off: this page comes from ./drivers/rtc, dated October 2026, under the Kernel API Manual banner. Bye bestie, go check those syncs πŸ«ΆπŸ’œ

πŸ“¦ where this page comes from