__rpmh_write(9)

💖 NAME 💖

okay so bestie, this is __rpmh_write — the double-underscore icon herself — and her whole job is literally cache and send the RPMH request ✨

---

🎀 SYNOPSIS 🎀

int __rpmh_write (const struct device *dev , enum rpmh_state state ,
struct rpmh_request *rpm_msg );

she takes three things and gives you back an int, that's the whole vibe 💅

---

🌸 ARGUMENTS 🌸

• dev — the device that's making the request, like the one actually asking for this 🫶
• state — the Active/Sleep request type, so she knows what kind of mood we're in
• rpm_msg — the actual data that needs to be sent (the cmds), the payload, the whole point 💅

---

🦋 DESCRIPTION 🦋

so here's the tea, bestie: __rpmh_write caches the RPMH request, and then she sends it if the state is ACTIVE_ONLY. that's it, that's the condition 🔥

but the SLEEP/WAKE_ONLY requests? nope, she does not send those to the controller at this time. they just sit there, cached, chilling 🙈

when you're actually ready to send those ones to the controller, you use rpmh_flush — that's her moment, not this function's moment, iykyk 💀

---

⭐ SEE ALSO ⭐

the kernel file for all of this lives at ./drivers/soc/qcom/rpmh.c, and she's got a whole friend group:

• struct cache_req(9)
• struct batch_cache_req(9)
• rpmh_read(9)
• rpmh_write_async(9)
• rpmh_write(9)
• rpmh_write_batch(9)
• rpmh_flush(9)
• rpmh_invalidate(9)

go say hi to all of them, they're iconic 👑

---

and that's the page, bestie 🧚 from ./drivers/soc/qcom, dated October 2026, and yes the title is still __rpmh_write(9) because we don't change the facts around here — periodt 💜💫