devm_clk_bulk_get_all(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 devm_clk_bulk_get_all(9) — Kernel API Manual 🌸

okay so first of all, bestie, we're in the Kernel API Manual, and this page is called devm_clk_bulk_get_all(9). it's a clock thing. a bulk clock thing. with managed vibes. stay with me 💅

✨ NAME ✨

devm_clk_bulk_get_all — managed get multiple clk consumers

like, you get ALL the clocks. and they're managed. and it slays 🎀

🌈 SYNOPSIS 🌈

int devm_clk_bulk_get_all (struct device *dev , struct clk_bulk_data **clks );

🦋 ARGUMENTS 🦋

  • dev — the device for the clock "consumer". yes the quotes are in the original, they're being cute about it, respect it 💖
  • clks — pointer to the clk_bulk_data table of the consumer. this is where the goods get stored, no cap

💅 DESCRIPTION 💅

okay so here's the tea 🍓 — this function returns a positive value for the number of clocks obtained, and the clock references get stored in the clk_bulk_data table in the clks field. like a little clock goodie bag.

it returns 0 if there're none (sad, but valid, vibe check passed 🫶) and a negative value if something failed (not slay, but at least you know 😭).

so this helper function is literally for letting drivers get several clk consumers in one operation with management. the whole point, the entire main-character energy of it: the clks will automatically be freed when the device is unbound. no manual cleanup arc. no leaking era. we love to see it 👑

⭐ SEE ALSO ⭐

bestie here's the whole extended friend group, the entire group chat of clock-related functions, and I am NOT leaving anyone out, they all get an invite 🎀

ngl the way there are like sixty friends on this list and every single one is a (9)… iconic. group chat is THRIVING 💀💜

and that's the page!! this one lives in ./include/linux and it's dated October 2026, so like, future-coded but the clock knowledge is timeless ✨ mwah, go free your bulk clocks responsibly, bestie 🧚‍♀️💖

📦 where this page comes from