clk_disable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME

clk_disable β€” the "okay bestie we're done here" call that tells the system your clock source is no longer required ✨

(also hi, this is a page from the Kernel API Manual, and it's lowkey one of the most important little functions you'll ever call 🫢)


🌸 SYNOPSIS

void clk_disable (struct clk *clk );

πŸŽ€ ARGUMENTS

  • clk β€” the clock source, bestie. that's your whole argument. one (1) clock. iconic minimalism fr πŸ’…

πŸ¦‹ DESCRIPTION

Okay so basically: you're informing the system that a clock source is no longer required by a driver, and that it may be shut down. that's it, that's the vibe. you're releasing your claim on it 🌈

The slay part? It may be called from atomic contexts. yes literally. atomic. no sleeping, no blocking, she just works πŸ’–

Implementation detail (iykyk): if the clock source is shared between multiple drivers, then clk_enable calls must be balanced by the same number of clk_disable calls for the clock source to actually be disabled. like. it's a ratio thing. you enable once, you disable once. enable twice? you owe two disables. don't leave the clock hanging, it's giving unbalanced energy and that's not the main character move 😭

⭐ SEE ALSO

Kernel file ./include/linux/clk.h πŸ’« and honestly the whole extended clk cinematic universe:


and that's the whole page, bestie 🧚 no cap, you're now officially clock-literate πŸ’œ

Source: ./include/linux β€” dated October 2026 πŸ“ (yes the date is in the future, the kernel docs said so, not me πŸ™ˆ). go forth and balance your enables and disables, queen πŸ‘‘

πŸ“¦ where this page comes from