dev_pm_qos_update_request(9)

📦 version 7.3.1, in nixpkgs unstable

💅 dev_pm_qos_update_request(9) 💅

okay so bestie, welcome to the Kernel API Manual, section 9 — this is the glow-up page for dev_pm_qos_update_request, and yes it's giving "small function, big responsibilities" energy. let's get into it 🎀

✨ NAME ✨

dev_pm_qos_update_request — modifies an existing qos request. that's it, that's the whole vibe check: it modifies, it does not create, it does not destroy. it's the middle child of the qos family and honestly? iconic. 👑

🌸 SYNOPSIS 🌸

int dev_pm_qos_update_request (struct dev_pm_qos_request *req , s32
new_value );

look at her. returns an int, takes two things, slays. 🦋

🫶 ARGUMENTS 🫶

  • req — handle to list element holding a dev_pm_qos request to use. like, this is your little ticket to the request you already made, bestie. no ticket, no entry. 🎟️
  • new_value — defines the qos request. it's an s32, it's the new number, it's literally setting the whole mood of the constraint. ✨

💖 DESCRIPTION 💖

Updates an existing dev PM qos request along with updating the target value. so like, the request already exists (you made it earlier with dev_pm_qos_add_request), and this is you going "hey bestie, change of plans, new number please." 💅

Attempts are made to make this code callable on hot code paths. that's right — no cap, this thing is built to run fast and often, so don't be shy with it. 🔥

the returns, and honestly this is the part everyone asks about, so listen up:

  • 1 — the aggregated constraint value has changed. a real shift, a genuine moment, main character energy. 👑
  • 0 — the aggregated constraint value has not changed. same as it ever was. a little anticlimactic but we respect it. 💀
  • -EINVAL — in case of wrong parameters. you passed something cursed. 🙈
  • -ENODEV — if the device has been removed from the system. she's gone, the device left the chat. 😭
⚠️ important bestie!! Callers should ensure that the target device is not RPM_SUSPENDED before using this function for requests of type DEV_PM_QOS_FLAGS. seriously. do the vibe check on the device state first. not me warning you twice. 🌈

🧚 SEE ALSO 🧚

Kernel file ./drivers/base/power/qos.c — and the whole friend group, fr fr:

iykyk 💜

okay that's the page!! source: ./drivers/base/power, dated October 2026, still serving looks in the Kernel API Manual 🎀 go update those requests, bestie, you're literally gonna slay 🦋💖✨

📦 where this page comes from