rpmh_rsc_cpu_pm_callback(9)

💅 rpmh_rsc_cpu_pm_callback(9) 💅

✨ NAME ✨

okay so this is the Kernel API Manual page for rpmh_rsc_cpu_pm_callback — Check if any of the AMCs are busy. That's the whole assignment, bestie. 💅

🌸 SYNOPSIS 🌸

int rpmh_rsc_cpu_pm_callback (struct notifier_block *nfb , unsigned long
       action , void *v );

💅 ARGUMENTS 💅

• nfb — Pointer to the notifier block in struct rsc_drv. 🫶
• action — CPU_PM_ENTER, CPU_PM_ENTER_FAILED, or CPU_PM_EXIT. ✨
• v — Unused. 🙈

🦋 DESCRIPTION 🦋

This function is literally given to cpu_pm_register_notifier so we can be informed about when CPUs go down. When all CPUs go down, we know no more active transfers will be started, so we write sleep/wake sets. no cap, that's the vibe.

It gets called from cpuidle code paths and also at system suspend time. 🌸

If it's the last CPU going down and the AMCs are not busy, then it writes cached sleep and wake messages to TCSes. The firmware then takes care of triggering them when entering deepest low power modes. that's the main character behavior 🔥

🎀 RETURN 🎀

See cpu_pm_register_notifier. That's the whole return tea — iykyk. 💜

🔥 SEE ALSO 🔥

Kernel file ./drivers/soc/qcom/rpmh-rsc.c is where all this lore lives, and the whole friend group is:

• 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_write_ctrl_data(9)
• rpmh_rsc_ctrlr_is_busy(9)
• rpmh_rsc_write_next_wakeup(9)
• rpmh_rsc_pd_callback(9)

okay bestie, that's the whole page 💖 this one comes from ./drivers/soc/qcom, dated October 2026 — go off and be iconic with your notifier 🎀