rpmh_write(9)

✨ NAME ✨

okay so bestie, this is rpmh_write(9) from the Kernel API Manual — the function whose whole job is: write a set of RPMH commands and block until response. yes, that's the name line, and we're obsessed. 💅

🦋 SYNOPSIS 🦋

int rpmh_write (const struct device *dev , enum rpmh_state state , const
       struct tcs_cmd *cmd , u32 n );

🎀 ARGUMENTS 🎀

• dev — the device making the request. main character device energy. 💖
• state — active/sleep set. pick your era. ✨
• cmd — the payload data. the actual goods. 🎀
• n — the number of elements in cmd. count 'em, bestie. 🦋

🌸 DESCRIPTION 🌸

okay so real talk: May sleep. Do not call from atomic contexts. that's the whole vibe check, and it's highkey important — this function is allowed to nap, so keep it out of atomic contexts, fr fr. 😭

🚨 May sleep. Do not call from atomic contexts. no cap, this one matters.

🔥 SEE ALSO 🔥

• Kernel file ./drivers/soc/qcom/rpmh.c
• struct cache_req(9)
• struct batch_cache_req(9)
• __rpmh_write(9)
• rpmh_read(9)
• rpmh_write_async(9)
• rpmh_write_batch(9)
• rpmh_flush(9)
• rpmh_invalidate(9)

and that's the page, bestie 🫶 source/version vibes: source path ./drivers/soc/qcom, date October 2026, and the page is rpmh_write(9) — periodt. ✨