dev_pm_qos_expose_flags(9)

💖 dev_pm_qos_expose_flags(9) 💖

okay so welcome to the Kernel API Manual page for dev_pm_qos_expose_flags(9) — this is the one about exposing a device's PM QoS flags to user space. it's giving kernel power-management realness, and we're keeping every detail exactly where it belongs. no cap. 💅

🌸 NAME 🌸

dev_pm_qos_expose_flags — expose PM QoS flags of a device to user space. ✨

🎀 SYNOPSIS 🎀

int dev_pm_qos_expose_flags (struct device *dev , s32 val );

that's the whole signature, bestie — spacing and all. 🫶

🦋 ARGUMENTS 🦋

• dev — the struct device * whose PM QoS flags are getting exposed to user space. main character device energy, honestly. 👑
• val — the initial values of the flags. it's an s32, and it is literally the starting flag values. 🚩

🔥 SEE ALSO 🔥

Kernel file ./drivers/base/power/qos.c is the spot, and the see-also squad is:

• __dev_pm_qos_flags(9)
• dev_pm_qos_flags(9)
• __dev_pm_qos_resume_latency(9)
• dev_pm_qos_read_value(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_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)

and that's the whole page, bestie 🫶 the source/version is ./drivers/base/power, it's dated October 2026, and the entry is still dev_pm_qos_expose_flags(9). slay 💅✨