pm_clk_acquire(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 pm_clk_acquire(9) — the pm_clk_acquire page, bestie edition 🌸

okay so real talk, this is a page from the Kernel API Manual (yes, the fancy one) and it's literally about grabbing a device clock. short page, but iconic. let's get into it 💅

✨ NAME ✨

pm_clk_acquire — acquire a device clock. that's it. that's the whole vibe. you're getting a clock for a device, periodt 🕐💖

✨ SYNOPSIS ✨

void pm_clk_acquire (struct device *dev , struct pm_clock_entry *ce );

not me just copying this exactly because the facts do not change, only the energy does 😌 take a sec, breathe it in. it returns void, meaning it gives you nothing back — the acquiring IS the moment, main character energy fr fr.

🦋 ARGUMENTS 🦋

  • dev — the device whose clock is gonna get acquired. like, this is the device in question, the one we're doing all this for 🫶
  • ce — the PM clock entry that corresponds to that clock. so ce is the matching entry, the little buddy that lines up with the clock. iykyk 💫
bestie pls note: these two go together, dev and ce, no cap. dev is the device, ce is the PM clock entry for the clock. that's the whole cast 🌈

💜 SEE ALSO 💜

okay this is the part where the page just lists everyone at the function party and honestly? obsessed. the kernel file lives at ./drivers/base/power/clock_ops.c and here's the whole squad 🎀:

and yes, pm_clk_notify(9) really does show up twice in the original list — i'm not gaslighting you, it's literally there twice, so it's here twice. we don't erase entries in this house 💀✨

🧚 sign-off 🧚

this little page comes from ./drivers/base/power and it's dated October 2026, filed under pm_clk_acquire(9) in the Kernel API Manual. slay, go acquire ur clocks responsibly, mwah 💖🎀🔥

📦 where this page comes from