dev_pm_qos_...atency_limit(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 dev_pm_qos_expose_latency_limit — Kernel API Manual 💅

okay so first things first, bestie: the title up top got a little chopped (dev_pm_qos_...atency_limit(9), the way it's giving "text message that got cut off mid-word" 😭) but the actual function is the whole entire dev_pm_qos_expose_latency_limit, and we're living in the Kernel API Manual, and yes this is a whole page about it. strap in 🎀

✨ NAME ✨

dev_pm_qos_expose_latency_limit — literally exposes the PM QoS latency limit to user space. that's the whole vibe. it puts the limit out there so userspace can see it / touch it. exposing. iconic behaviour tbh 🫶

✨ SYNOPSIS ✨

int dev_pm_qos_expose_latency_limit (struct device *dev , s32 value );

like, that's the signature, no cap. int going in, int coming out, two args, periodt 💜

✨ ARGUMENTS ✨

  • dev — the struct device whose PM QoS latency limit is the one being exposed to user space. it's her limit, she's the main character here 👑
  • value — the initial value of the latency limit. like, the starting number before anything else happens. the origin story, if you will 🌱

✨ SEE ALSO ✨

the whole friend group, fr fr — this lives in the kernel file ./drivers/base/power/qos.c, and honestly you should go meet the rest of the squad:

bestie note: dev_pm_qos_hide_latency_limit(9) is right there in the list and it's literally the reverse of this one — yin and yang, expose and hide, the duality of ~~man~~ kernel 🦋

so yeah, that's the page 💖 it's short, it's sweet, it's from ./drivers/base/power, dated October 2026, and the whole thing still answers to the name dev_pm_qos_...atency_limit(9) — truncated title and all, she's still slaying ✨ mwah, go read the qos.c file, ily, bye 🎀💅

📦 where this page comes from