rpmh_rsc_write_ctrl_data(9)

💅 rpmh_rsc_write_ctrl_data — the Kernel API Manual page, bestie edition 🎀

okay so you're looking at rpmh_rsc_write_ctrl_data(9), which lives in the Kernel API Manual, and honestly? It's giving "quiet little helper that does one very specific thing." Let me tell you everything ✨

---

🌸 NAME 🌸

rpmh_rsc_write_ctrl_data — write the request to the controller but don't trigger it. That's the whole vibe. It writes. It does not poke the trigger. No cap. 🫶

---

🦋 SYNOPSIS 🦋

int rpmh_rsc_write_ctrl_data(struct rsc_drv *drv, const struct tcs_request *msg);

---

🎀 ARGUMENTS 🎀

• drv — the controller. Your main character here 💖
• msg — the data that's actually getting written to the controller.

---

✨ DESCRIPTION ✨

Lowkey this one is a very specific-use function, so listen up:

It should only be called for sleep/wake state — never active-only state. Periodt. 🙅‍♀️

⚠️ The caller has to make sure, themselves, that no other RPMH actions are happening and that the controller is idle when this function is called, because it runs lockless. That's a big deal, bestie — the function isn't gonna check for you, so do the vibe check yourself first. 😭

---

💀 RETURN 💀

0 if there's no error; otherwise -error.

---

👑 SEE ALSO 👑

Kernel file ./drivers/soc/qcom/rpmh-rsc.c, plus this whole friend group:

• tcs_invalidate(9)
• rpmh_rsc_invalidate(9)
• get_tcs_for_msg(9)
• get_req_from_tcs(9)
• __tcs_set_trigger(9)
• enable_tcs_irq(9)
• tcs_tx_done(9)
• __tcs_buffer_write(9)
• check_for_req_inflight(9)
• find_free_tcs(9)
• claim_tcs_for_req(9)
• rpmh_rsc_send_data(9)
• find_slots(9)
• rpmh_rsc_ctrlr_is_busy(9)
• rpmh_rsc_write_next_wakeup(9)
• rpmh_rsc_cpu_pm_callback(9)
• rpmh_rsc_pd_callback(9)

---

🌈 that's the whole page, bestie! 🍓

Sign-off time 🎀 this one comes from ./drivers/soc/qcom, dated October 2026, and it's page rpmh_rsc_write_ctrl_data(9) of the Kernel API Manual. Slay, go forth and write your control data responsibly 💜🧚