dev_pm_qos_remove_request(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, you're on the dev_pm_qos_remove_request(9) page in the Kernel API Manual, and it's lowkey all about taking an existing qos request out of the mix and refreshing the target value. slay πŸ’…


✨ NAME ✨

dev_pm_qos_remove_request β€” modifies an existing qos request


🌸 SYNOPSIS 🌸

int dev_pm_qos_remove_request (struct dev_pm_qos_request *req );

πŸŽ€ ARGUMENTS πŸŽ€

  • req β€” handle to request list element. literally your little handle to the request list element, bestie 🫢

πŸ’– DESCRIPTION πŸ’–

It will remove the pm qos request from the list of constraints and recompute the current target value. Call this on slow code paths β€” yes, this one is giving slow-path main character energy, so use it there. 🐒✨

Return values, no cap:

  • 1 if the aggregated constraint value has changed
  • 0 if the aggregated constraint value has not changed
  • -EINVAL in case of wrong parameters
  • -ENODEV if the device has been removed from the system
⚠️ Callers should ensure that the target device is not RPM_SUSPENDED before using this function for requests of type DEV_PM_QOS_FLAGS. this is the β€œcheck the vibe before you touch it” part, fr fr πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./drivers/base/power/qos.c


mwah πŸ’‹ this little icon is filed under ./drivers/base/power, and the date on it is October 2026 β€” periodt. πŸŒˆπŸ‘‘

πŸ“¦ where this page comes from