omap2_dflt_clk_disable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… omap2_dflt_clk_disable(9) ✨

okay so bestie, welcome to the Kernel API Manual β€” this is the page for omap2_dflt_clk_disable, and yes it's giving exactly what you think it's giving: turning a clock off. πŸŽ€


🌸 NAME 🌸

omap2_dflt_clk_disable β€” disable a clock in the hardware πŸ’€


✨ SYNOPSIS ✨

void omap2_dflt_clk_disable (struct clk_hw *hw );

like, that's the whole signature. void in, void out, no return value, no drama. 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • hw β€” a struct clk_hw *, i.e. the pointer to the clock you wanna disable. that's the one, bestie. πŸ‘‘

πŸ’– DESCRIPTION πŸ’–

So what this does is disable the clock hw in the hardware β€” literally just, off. bye. πŸ’€

Then it calls into the OMAP clockdomain code to "disable" the corresponding clockdomain, but only if all the clocks/hwmods in that clockdomain are now disabled. like it's a whole vibe check for the clockdomain: everyone asleep? then the 'domain sleeps too. 😴✨

No return value. nothing comes back. it's giving "I did the thing and I don't need applause" energy. πŸ’…


🌈 SEE ALSO 🌈

like the whole friend group fr fr 🫢 go read omap2_dflt_clk_enable(9) next, it's the main character counterpart to this one. πŸ‘‘


okay that's the page!! 🧚 source/version lives at ./drivers/clk/ti and it's dated October 2026, and the title again for the road: omap2_dflt_clk_disable(9). mwah πŸ’‹β­

πŸ“¦ where this page comes from