_clkdm_del_wkdep(9)

📦 version 7.3.1, in nixpkgs unstable

💅 _clkdm_del_wkdep(9) — the kernel API manual, bestie edition 💅

okay so you're in the Kernel API Manual and the page is literally called _clkdm_del_wkdep. yes the leading underscore is part of the name, we don't make the rules (we absolutely make the rules, but not this one). anyway. it removes a wakeup dependency. 🔥

✨ NAME ✨

_clkdm_del_wkdep — remove a wakeup dep from clkdm2 to clkdm1 (lockless)

like, the lockless version, okay? the lock is somebody else's problem. main character energy but respectfully. 🫶

🌸 SYNOPSIS 🌸

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

two struct clockdomain * pointers walk into a function. this is where they get un-linked. 🦋

🎀 ARGUMENTS 🎀

  • clkdm1 — the dependent one, the one being woken up. literally wake this struct clockdomain * up. 💤➡️✨
  • clkdm2 — the source one, the one doing the waking. when this struct clockdomain * wakes up, that's the whole vibe trigger. ⏰

💖 DESCRIPTION 💖

bestie. this removes a wakeup dependency — the kind that makes clkdm1 wake up whenever clkdm2 wakes up. we are literally severing that link. no more "u up?" between these two clockdomains. 😭

so if clkdm2 wakes up, clkdm1 used to wake up too. now it doesn't, because you called this. slay. 💅

the return values, and pls memorize these because they matter:

  • -EINVAL — you handed it invalid clockdomain pointers. rude. 🙈
  • -ENOENT — clkdm2 cannot wake up clkdm1 in hardware. like the hardware just doesn't support that relationship, so there's nothing to remove. 💀
  • 0 — success. we ate. 🔥

👑 SEE ALSO 👑

the kernel file lives at ./arch/arm/mach-omap2/clockdomain.c and honestly the whole friend group is here:

no cap, that's all of them, i counted. 🧚

and that's the page!! this one came from ./arch/arm/mach-omap2 and it's dated October 2026, which is so far ahead it's giving time traveler. mwah, go remove some wakeup deps responsibly bestie 💜🎀⭐

📦 where this page comes from