__tcs_buffer_write(9)
π __tcs_buffer_write(9) β like, the kernel API manual bestie π
okay so this page lives in the Kernel API Manual (section 9, function girlies only β¨) and it's all about __tcs_buffer_write. let's get into it π«Ά
β¨ NAME β¨
__tcs_buffer_write β write to TCS hardware from a request; don't trigger. like, you're staging the vibe, not sending it π
πΈ SYNOPSIS πΈ
void __tcs_buffer_write (struct rsc_drv *drv , int tcs_id , int cmd_id ,
const struct tcs_request *msg );
π¦ ARGUMENTS π¦
drvβ the controller. the main character, fr. πtcs_idβ the global ID of this TCS. its little passport number πcmd_idβ the index within the TCS to start writing. where in the lineup we start π¬msgβ the message we wanna send, which will contain several addr/data pairs to program (but few enough that they all fit in one TCS). like packing a carry-on β cute, but there's a limit πββοΈ
π DESCRIPTION π
this one's used for all types of transfers β active, sleep, and wake. all of them. periodt π«Ά
β SEE ALSO β
kernel file ./drivers/soc/qcom/rpmh-rsc.c β go read her, she ate π₯
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)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)
ngl bestie, that whole cast of characters is a whole friend group β go say hi to each one π§
and that's the page!! mwah π sourced straight from ./drivers/soc/qcom, dated October 2026 β no cap, see u next time ππ
π¦ 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