clkdm_clk_disable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

clkdm_clk_disable(9) πŸ’…

okay bestie, welcome to the clkdm_clk_disable page from the Kernel API Manual β€” lowercase girlies, this one's a function, not a command, so buckle up πŸŽ€


✨ NAME ✨

clkdm_clk_disable β€” remove an enabled downstream clock from this clkdm 🫢


🌸 SYNOPSIS 🌸

int clkdm_clk_disable (struct clockdomain *clkdm , struct clk *clk );

like, that's the whole vibe. two args, one int coming back at you ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • clkdm β€” a struct clockdomain * 🏠 the clockdomain we're messing with, main character energy
  • clk β€” a struct clk * of the disabled downstream clock πŸ•°οΈ yes it's the disabled one, that's not a typo, that's the whole point

πŸ”₯ DESCRIPTION πŸ”₯

so here's the tea β˜• β€” when clk gets disabled, you decrement the usecount of this clockdomain, clkdm. literally that's it, that's the job. it's intended to be called by clk_disable code, so like, don't just call it because you feel like it, iykyk πŸ’…

and if the clockdomain usecount goes all the way to 0? two possibilities depending on the vibe:

  • software-supervised mode β†’ put the clockdomain to sleep 😴
  • hardware-supervised mode β†’ remove the clkdm autodependencies πŸ”—

now the return values, and this part is important bestie, don't skip πŸ™ˆ

  • returns -EINVAL if you passed null pointers (not me passing null pointers 😭)
  • returns -ERANGE if the clkdm usecount underflows πŸ’€ like it went below where it should, that's bad
  • returns 0 upon success ✨ or if the clockdomain is in hwsup idle mode πŸ‘‘

so yeah, 0 is the slay outcome, negative numbers are the "girl what" outcomes πŸ“


πŸ’œ SEE ALSO πŸ’œ

all the siblings, the whole friend group, no one left out 🫢 the kernel file is ./arch/arm/mach-omap2/clockdomain.c and here's everybody:


ok that's the whole page bestie, go forth and decrement responsibly πŸ’–

that's a wrap from the ./arch/arm/mach-omap2 girlies, dated October 2026, version vibes included β€” mwah, mwah, periodt πŸ‘‘πŸ’…

πŸ“¦ where this page comes from