clkdm_read_wkdep(9)

📦 version 7.3.1, in nixpkgs unstable

💅 clkdm_read_wkdep 💅

okay so bestie, welcome to the Kernel API Manual — yes, THE manual, the one and only ✨. today's main character is clkdm_read_wkdep, and honestly? she's a little detective. she just wants to know if one clockdomain is gonna wake up another one. lowkey iconic.

🌸 NAME 🌸

clkdm_read_wkdep — read wakeup dependency state from clkdm2 to clkdm1

like, "hey, is clkdm1 gonna get woken up by clkdm2 or not" — that's her whole job 🫶

✨ SYNOPSIS ✨

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

🎀 ARGUMENTS 🎀

  • clkdm1 — the *struct clockdomain ** that's gonna get woken up, aka the dependent one 🥺 she's the one who wakes
  • clkdm2 — the *struct clockdomain ** that does the waking, aka the source 😤 she's the one who's up first

🦋 DESCRIPTION 🦋

So here's the vibe check 🔍: this returns 1 if there's a hardware wakeup dependency existing where clkdm1 will be awoken when clkdm2 wakes up. Basically if the dependency is real, you get a 1 and she ate 💅

You get 0 if the dependency is not set. no dependency, no drama.

You get -EINVAL if either clockdomain pointer is invalid — like, bestie, those are not real pointers, try again 🙈

And you get -ENOENT if the hardware is literally incapable. it's not her fault, the hardware just can't 💀

REVISIT: rn this function only represents software-controllable wakeup dependencies. Wakeup dependencies that are fixed in hardware are not yet handled here — so don't come for her about those, she's very upfront about it ✨

🌈 SEE ALSO 🌈

Kernel file ./arch/arm/mach-omap2/clockdomain.c — and the whole friend group, fr fr:

alright bestie, that's the whole page, no cap 🧚💖 this came out of ./arch/arm/mach-omap2, dated October 2026, and it's filed under clkdm_read_wkdep(9) — periodt, go read your wakeup deps responsibly 👑🍓

📦 where this page comes from