rpmh_rsc_ctrlr_is_busy(9)
β¨ rpmh_rsc_ctrlr_is_busy(9) β¨
okay so bestie, this page lives in the Kernel API Manual, and itβs all about checking whether the AMCs are busy. tiny function, kinda important vibe check π
π NAME π
rpmh_rsc_ctrlr_is_busy β check if any of the AMCs are busy. π«Ά
πΈ SYNOPSIS πΈ
bool rpmh_rsc_ctrlr_is_busy (struct rsc_drv *drv );
π ARGUMENTS π
drvβ the controller π
π¦ DESCRIPTION π¦
This checks if any of the AMCs are busy handling ACTIVE sets. literally thatβs the whole assignment. β¨
It gets called from the last cpu powering down before flushing SLEEP and WAKE sets. if the AMCs are busy, the controller can not enter power collapse, so the move is to deny from the last cpuβs pm notification. no cap, thatβs the important part π₯
π CONTEXT π
Must be called with the drv->lock held. π
like, do not skip this. the lock is not optional, bestie π
π RETURN π
Falseβ AMCs are idle π΄Trueβ AMCs are busy π
π SEE ALSO π
Kernel file ./drivers/soc/qcom/rpmh-rsc.c, plus the whole squad: 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_write_next_wakeup(9), rpmh_rsc_cpu_pm_callback(9), rpmh_rsc_pd_callback(9) π§π
kisses from the Kernel API Manual π β source/version spot: ./drivers/soc/qcom, dated October 2026. periodt π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms