ti_sci_cmd_set_event_map(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

bestie, welcome to the Kernel API Manual page for ti_sci_cmd_set_event_map(9) πŸ’–. This function is literally here to configure an event based irq route between the requested source and the Interrupt Aggregator. that's the whole vibe, no cap.


πŸ¦‹ SYNOPSIS πŸ¦‹

okay so here's the exact signature, and yes every little comma matters:

int ti_sci_cmd_set_event_map (const struct ti_sci_handle *handle , u16
       src_id , u16 src_index , u16 ia_id , u16 vint , u16 global_event , u8
       vint_status_bit );

πŸŽ€ ARGUMENTS πŸŽ€

here's the cast of characters, and every single one is important:

  • handle β€” pointer to the TISCI handle. that's your entry point, bestie.
  • src_id β€” device ID of the IRQ source.
  • src_index β€” IRQ source index within the source device.
  • ia_id β€” device ID of the IA, if the IRQ flows through this IA.
  • vint β€” virtual interrupt to be used within the IA.
  • global_event β€” global event number to be used for the requesting event.
  • vint_status_bit β€” virtual interrupt status bit to be used for the event.

πŸ’– RETURN πŸ’–

0 if all went fine, else return appropriate error. that's the vibe check: 0 is slay, anything else is the kernel telling you something went sideways 😭.


🌈 SEE ALSO 🌈

so many iconique neighbors, fr fr:


xoxo, your kernel bestie πŸ«ΆπŸ’… β€” this one comes from ./drivers/firmware, dated October 2026, and signs off as ti_sci_cmd_set_event_map(9) βœ¨πŸ¦‹

πŸ“¦ where this page comes from