dev_pm_qos_read_value(9)
π dev_pm_qos_read_value(9)
okay so first things first, this is a page from the Kernel API Manual (yes, that manual, the big serious one, but we're gonna make it cute) π
β¨ NAME β¨
dev_pm_qos_read_value β bestie, this one gets you the PM QoS constraint for a given device, and likeβ¦ it's the locked version, mmkay? π no cap.
πΈ SYNOPSIS πΈ
s32 dev_pm_qos_read_value (struct device *dev , enum dev_pm_qos_req_type type );
look at her go, she's giving "two arguments, zero drama" π
π¦ ARGUMENTS π¦
devβ the device you wanna get the PM QoS constraint value for. literally just hand her the device π«Άtypeβ the QoS request type. that's the vibe of the request you're asking about β¨
π SEE ALSO π
the whole friend group, in the kernel file ./drivers/base/power/qos.c β go say hi to all of them, they're iconic:
__dev_pm_qos_flags(9)dev_pm_qos_flags(9)__dev_pm_qos_resume_latency(9)apply_constraint(9)dev_pm_qos_constraints_destroy(9)dev_pm_qos_add_request(9)__dev_pm_qos_update_request(9)dev_pm_qos_update_request(9)dev_pm_qos_remove_request(9)dev_pm_qos_add_notifier(9)dev_pm_qos_remove_notifier(9)dev_pm_qos_add_ancestor_request(9)dev_pm_qos_expose_latency_limit(9)dev_pm_qos_hide_latency_limit(9)dev_pm_qos_expose_flags(9)dev_pm_qos_hide_flags(9)dev_pm_qos_update_flags(9)dev_pm_qos_get_user_latency_tolerance(9)dev_pm_qos_update_user_latency_tolerance(9)dev_pm_qos_expose_latency_tolerance(9)dev_pm_qos_hide_latency_tolerance(9)
okay that's the whole page bestie, go forth and read those values π
sign-off szn: this one lives in ./drivers/base/power, and the date on it is October 2026 β so likeβ¦ mark your calendars, it's giving future energy π§ββοΈ mwah π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms