dev_pm_qos_...stor_request(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dev_pm_qos_...stor_request(9)

okay so bestie, welcome to the Kernel API Manual πŸŽ€ β€” yes we're reading kernel docs together, this is our bonding era, no cap.


✨ NAME ✨

dev_pm_qos_add_ancestor_request β€” literally adds a PM QoS request for a device's ancestor. That's it, that's the whole vibe. πŸ‘‘


🌸 SYNOPSIS 🌸

int dev_pm_qos_add_ancestor_request (struct device *dev , struct
       dev_pm_qos_request *req , enum dev_pm_qos_req_type type , s32 value );

like… yes she's a function, yes she returns an int, we move πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the device whose ancestor we're adding the request for. not the device itself, bestie, the ancestor β€” read it again, iykyk πŸ‘€
  • req β€” pointer to the preallocated handle. preallocated!! you gotta bring your own handle, it's giving bring-your-own-beverage πŸ₯€
  • type β€” the type of the request. that's the enum dev_pm_qos_req_type energy ✨
  • value β€” the constraint latency value, a lil s32. it's the number, it's the moment πŸ“

πŸ’œ SEE ALSO πŸ’œ

Kernel file ./drivers/base/power/qos.c β€” and honestly the whole friend group showed up for this one, so let's give them all their moment 🫢:

like, the whole squad. main character energy all around πŸ‘‘


reminder bestie: this page lives under ./drivers/base/power, and it's dated October 2026 β€” so yeah, future-coded of it πŸ’€πŸ“…

and that's the page!! go forth and add those ancestor requests, you absolute icon πŸŒˆπŸ¦‹ mwah πŸ’–

πŸ“¦ where this page comes from