STRUCT RPMH_REQUEST(9)

✨ struct rpmh_request(9) ✨

okay so bestie, welcome to the Kernel API Manual entry for struct rpmh_request 🎀 — literally the little message bundle that gets sent over to rpmh-rsc. it's giving "envelope with your whole request inside" energy, and honestly? iconic 🦋.

---

💌 NAME

struct rpmh_request — the message to be sent to rpmh-rsc 📨

---

🌸 SYNOPSIS

struct rpmh_request {
    struct tcs_request msg;
    struct tcs_cmd cmd[MAX_RPMH_PAYLOAD];
    struct completion *completion;
    const struct device *dev;
    bool needs_free;
 };

no cap, that's the whole shape of it. copy it exactly, don't be out here renaming fields 🙈.

---

👑 Members

• msg — the request itself, the main character of the struct 💅
• cmd — the payload that will be part of the msg, i.e. the actual goodies riding along with the request 🍓
• completion — triggered when request is done ✨ (so like, the "we're so back" notification)
• dev — the device making the request, aka who's asking 🫶
• needs_free — check to free dynamically allocated request object 🌈 — yes queen, do your cleanup, memory leaks are not the vibe 💀

lowkey important: that last one is a flag you check before freeing a dynamically allocated request object. keep it tidy 🧚

---

🔭 SEE ALSO

Kernel file ./drivers/soc/qcom/rpmh-internal.h — plus these absolute legends:

• struct tcs_group(9)
• struct rpmh_ctrlr(9)
• struct rsc_drv(9)

go read them, iykyk 📚💜

---

that's the whole page bestie, no filler, fr fr 💖

source: ./drivers/soc/qcom · dated October 2026 · struct rpmh_request(9)

mwah, go slay your RPMh requests 👑💅✨