dev_pm_opp_g...lock_latency(9)

📦 version 7.3.1, in nixpkgs unstable

💜 dev_pm_opp_get_max_clock_latency — the vibe check

okay bestie, so this one lives in the Kernel API Manual and the page header is literally dev_pm_opp_g...lock_latency(9) — yes the name is truncated with ..., that's just how the man page template does it, don't come for her 💅. Anyway. Sit down, hydrate, and let's talk clock latency.

✨ NAME ✨

dev_pm_opp_get_max_clock_latency — Get max clock latency in nanoseconds 🕐✨

🦋 SYNOPSIS 🦋

unsigned long dev_pm_opp_get_max_clock_latency (struct device *dev );

like literally that's it. one function, one argument, one unsigned long coming back at you 🫶

🎀 ARGUMENTS 🎀

  • dev — the device for which we do this operation, i.e. the main character of this whole story. you hand her the device, she tells you about her clock latency. iconique.

🌸 RETURN 🌸

This function returns the max clock latency in nanoseconds. no cap, that's the whole return value. nanoseconds. tiny little units. slay ⭐

🔥 SEE ALSO 🔥

bestie this list is LONG, so buckle up — everything here is (9) and yes I'm listing every single one because we don't do "etc." in this house 👑

like… 40+ cross-references. she's connected. she knows everybody. networking queen 🌈💅

ngl the only thing this page actually does is give you back a number in nanoseconds — but every single one of those SEE ALSO friends is a real function and you WILL be seeing them again, so maybe bookmark this page, bestie 🍓

that's the whole thing, no hidden lore 🧚 and before you go — this beauty is sourced from ./drivers/opp and stamped October 2026, filed under the ever-so-slightly-truncated dev_pm_opp_g...lock_latency(9). mwah, go get 'em 💖🎀

📦 where this page comes from