omap2_clkops_disable_clkdm(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… omap2_clkops_disable_clkdm(9) β€” Kernel API Manual energy ✨

Okay bestie, welcome to the omap2_clkops_disable_clkdm page β€” yes, that name is a whole mouthful, but we're gonna slay it together. It's giving kernel-internals realness, and honestly? Kinda iconic. πŸŽ€


🌸 NAME 🌸

omap2_clkops_disable_clkdm β€” decrement usecount on clkdm of @hw


✨ SYNOPSIS ✨

void omap2_clkops_disable_clkdm (struct clk_hw *hw );

πŸŽ€ ARGUMENTS πŸŽ€

  • hw β€” a struct clk_hw * for the clock that's being disabled πŸ’–

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the vibe: this function decrements the usecount of the clockdomain belonging to the clock that hw points at. Lowkey simple, highkey important. 🫢

And if that usecount hits 0? The clockdomain will be "disabled." Periodt. πŸ’…

It's only needed for clocks that don't use omap2_dflt_clk_disable as their disable function pointer. Like, if your clock is already doing the default thing, this is not your moment β€” no cap. πŸ™ˆ

Also: no return value. It's a void function, so don't go looking for a result, bestie. 😭


πŸ‘‘ SEE ALSO πŸ‘‘


And that's the whole page, bestie β€” fr fr. This little kernel moment comes from ./drivers/clk/ti, dated October 2026, and it's literally the omap2_clkops_disable_clkdm(9) manual page. Go off, clockdomain girlie. πŸ’œβœ¨πŸŒΈ

πŸ“¦ where this page comes from