clkdm_add_wkdep(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– clkdm_add_wkdep (9) πŸ’–

okay so bestie, this one's from the Kernel API Manual and it's literally about making one clockdomain wake up the second another one does. it's giving "i got you, you got me" energy fr fr 🫢


✨ NAME ✨

clkdm_add_wkdep β€” add a wakeup dependency from clkdm2 to clkdm1


✨ SYNOPSIS ✨

int clkdm_add_wkdep (struct clockdomain *clkdm1 , struct clockdomain *clkdm2 );

✨ ARGUMENTS ✨

  • clkdm1 β€” the dependent one, aka the struct clockdomain * we're waking up. she's the one who gets woken 🌸
  • clkdm2 β€” the source, aka the struct clockdomain * whose wakeup triggers everything. when she wakes up, the whole thing goes down πŸ‘‘

✨ DESCRIPTION ✨

okay so the vibe is: when the clockdomain represented by clkdm2 wakes up, wake up clkdm1. simple as that, no cap πŸ’…

this whole feature is implemented in hardware on the OMAP, and it exists to reduce the wakeup latency of the dependent clockdomain clkdm1. literally designed to make her wake up faster, iconic behavior honestly πŸ¦‹

and because nothing is free, here's the return-value tea:

  • -EINVAL β€” you handed it invalid clockdomain pointers πŸ™ˆ
  • -ENOENT β€” clkdm2 cannot wake up clkdm1 in hardware, so the hardware said "not me" πŸ’€
  • 0 β€” success, slay ✨

✨ SEE ALSO ✨

the whole friend group lives in the kernel file ./arch/arm/mach-omap2/clockdomain.c and honestly here's everyone:

bestie go read them all, i promise they're worth it πŸ”₯

and that's the whole page! πŸŽ€ this one came out of ./arch/arm/mach-omap2 and it's dated October 2026 β€” mwah, love that for us πŸ’œπŸ§š

πŸ“¦ where this page comes from