__tcs_set_trigger(9)

📦 version 7.3.1, in nixpkgs unstable

💅 __tcs_set_trigger 💅

okay so this page lives in the Kernel API Manual and it's all about __tcs_set_trigger — the little function that starts a transfer on a TCS, or un-sets the trigger on a TCS you borrowed. no cap, that's literally the whole NAME section. 🎀

✨ SYNOPSIS ✨

void __tcs_set_trigger (struct rsc_drv *drv , int tcs_id , bool trigger );

that's it, that's the whole signature. void return, no drama, she just does the thing. 🫶

🌸 ARGUMENTS 🌸

  • drv — the controller. the big boss. the main character, honestly. 👑
  • tcs_id — the global ID of this TCS. global, bestie, not local. don't get it twisted. 🦋
  • trigger — if true, then untrigger/retrigger. if false, then just untrigger. that's the whole vibe check right there. 💅

💖 DESCRIPTION 💖

so in the normal case — like, the everyday, nothing-weird-happening case — we only ever call this with "trigger=true" to start a transfer. and what that does is: it un-triggers/disables the TCS from the last transfer, then triggers/enables it for this transfer. out with the old, in with the new. slay. ✨

now, the plot twist 🌈: if we borrowed a wake TCS for an active-only transfer, we'll also call this function with "trigger=false" — and in that case it's just doing the un-trigger/disable, nothing else — before we go using that TCS for wake purposes again. she's being handed back, freshly un-triggered. responsible! 🧚

⚠️ important note, don't skip this one: the AP is only in charge of triggering active-only transfers. the AP never triggers sleep/wake values using this function. never ever. not even once. 😤

🔥 SEE ALSO 🔥

the kernel file ./drivers/soc/qcom/rpmh-rsc.c is where all the magic lives — here's the whole squad, and yes you need all of them:

iykyk, this is a whole friend group 💜

okay that's the page!! mwah 💋 this one came from ./drivers/soc/qcom, dated October 2026, and it's filed under __tcs_set_trigger(9) — go forth and trigger responsibly, bestie 🍓💫

📦 where this page comes from