ti_sci_inta_manage_event(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ti_sci_inta_manage_event β€” the kernel API manual, bestie edition πŸŽ€

Okay so picture this: you're deep in the kernel API manual (yes, that one, the ti_sci_inta_manage_event(9) page, we're literally here) and you need to, like, control an event based on an offset. That's the whole vibe. Let me walk you through it 🫢


✨ NAME ✨

ti_sci_inta_manage_event β€” control the event based on the offset. That's it, that's the function, no cap πŸ’…


🌸 SYNOPSIS 🌸

void ti_sci_inta_manage_event (struct irq_data *data , u32 offset );

Look at her. No return value, just vibes and two arguments. Iconic ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • data β€” pointer to the corresponding irq_data. It's the irq_data bestie, she's coming with you πŸŽ€
  • offset β€” the register offset using which the event is controlled. This is the little number that decides which event gets handled, iykyk πŸ’œ

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/irqchip/irq-ti-sci-inta.c, and honestly the whole friend group showed up for this one, so let's give them their moment:

Like, the whole squad. Read them all, bestie, they're all in ./drivers/irqchip together 🌈


Lowkey a whole interrupt-controller family tree in here. Go read the siblings, fr fr 🧚

Okay that's the page!! Written up in the kernel API manual, living in ./drivers/irqchip, dated October 2026, and signed off as ti_sci_inta_manage_event(9) β€” periodt πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from