__tcs_buffer_write(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __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 πŸ”₯


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