ti_sci_rx_callback(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– ti_sci_rx_callback (9) β€” Kernel API Manual πŸ’–

okay so bestie, you found the man page for ti_sci_rx_callback β€” it's the mailbox client callback that handles incoming messages, and honestly it's giving "small function, big job" energy πŸŽ€


✨ NAME ✨

ti_sci_rx_callback β€” the mailbox client callback for receive messages πŸ¦‹


🌸 SYNOPSIS 🌸

void ti_sci_rx_callback (struct mbox_client *cl , void *m );

yeah, that's the whole signature. two args, no return value, very demure, very mindful πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • cl β€” the client pointer 🫢
  • m β€” the mailbox message itself, like the actual payload that just showed up

πŸ‘‘ DESCRIPTION πŸ‘‘

So what it does: it takes one received message and processes it into the appropriate transfer information, then signals that the transfer is complete ✨ that's it, that's the whole vibe. a message comes in, it gets sorted into the right xfer, and the completion gets signalled. lowkey iconic for how much it does with so little 😌


⚠️ NOTE ⚠️

bestie listen to me. this function gets invoked in IRQ context β€” interrupt context, okay?? so it needs to be as optimal as possible. no cap. do NOT be doing slow, sleepy, heavy lifting in here πŸ’€ keep it lean, keep it fast, keep it interrupt-friendly πŸ”₯

🌈 SEE ALSO 🌈

everything else hanging out in the kernel file ./drivers/firmware/ti_sci.c and its whole friend group 🧚:


that's the whole page bestie, go be optimal in IRQ context πŸ’œ

sign-off szn ✨ this lil beauty lives under ./drivers/firmware and the date on it is October 2026 β€” yeah, future-coded, we know πŸ¦‹

πŸ“¦ where this page comes from