omap2_clkops_disable_clkdm(9)
π 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β astruct 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 π
- Kernel file
./drivers/clk/ti/clockdomain.c omap2_clkops_enable_clkdm(9)omap2_init_clk_clkdm(9)ti_dt_clockdomains_setup(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms