get_tcs_for_msg(9)
πΈ NAME πΈ
okay so bestie, welcome to the get_tcs_for_msg(9) page in the Kernel API Manual π. This function is literally here to Get the tcs_group used to send the given message. Thatβs the whole assignment, no cap periodt β¨
β¨ SYNOPSIS β¨
struct tcs_group * get_tcs_for_msg (struct rsc_drv *drv , const struct
tcs_request *msg );
copy-paste safe, bestie π«Ά
π ARGUMENTS π
drvβ The RSC controller. iconic controller behavior πmsgβ The message we want to send. the whole point π
π DESCRIPTION π
okay so normally this is pretty straightforward, except if we are trying to send an ACTIVE_ONLY message but don't have any active_only TCSes. Thatβs the little plot twist π β the vibe check gets spicy π₯
π«Ά RETURN π«Ά
A pointer to a tcs_group or an ERR_PTR. thatβs it, thatβs the return π
β¨
π₯ SEE ALSO π₯
Kernel file ./drivers/soc/qcom/rpmh-rsc.c β go read the source, bestie ππ
tcs_invalidate(9)rpmh_rsc_invalidate(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_cpu_pm_callback(9)rpmh_rsc_pd_callback(9)
byeee bestie β this page is from ./drivers/soc/qcom, dated October 2026, and itβs the get_tcs_for_msg(9) page. slay and stay safe out there π
π
π¦ 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