ti_sci_inta_free_irq(9)

📦 version 7.3.1, in nixpkgs unstable

🌸 ti_sci_inta_free_irq 💅

okay so bestie, you found a page from the Kernel API Manual and it's literally about releasing an IRQ in the INTA domain. it's giving cleanup era ✨ no cap, let's get into it 🫶

✨ NAME ✨

ti_sci_inta_free_irq — free an IRQ within the INTA domain 🎀

like, the whole entire point of this function is letting go and honestly? character development 💜

🦋 SYNOPSIS 🦋

void ti_sci_inta_free_irq (struct ti_sci_inta_event_desc *event_desc ,
       u32 hwirq );

note the void — this function does not return anything, it just does the thing and exits, main character energy 👑

🔥 ARGUMENTS 🔥

  • event_desc — pointer to the event_desc that needs to be freed. yes, the one you're done with. release it, bestie, it's not your responsibility anymore 😭
  • hwirq — the hwirq number within the INTA domain that needs to be freed. literally the specific one. don't free the wrong one, that's not slay 💀

🌈 SEE ALSO 🌈

so if you wanna go deeper (and ikyk you do 👀), go read the kernel file ./drivers/irqchip/irq-ti-sci-inta.c — it's the source of truth fr fr.

and then the whole friend group 💖:

like a whole squad of INTA functions, obsessed 🧚

💡 friendly reminder: there are no options, no return values, no environment variables, exit statuses or signals on this page — it's just the one function signature, the two arguments, and the see-also list. that's the whole vibe. periodt 🍓

and that's the page, bestie!! 💅 big smooch from ./drivers/irqchip 🫶 — this iconic lil' doc was served up in October 2026 under the name ti_sci_inta_free_irq(9), and it ate, no crumbs ⭐🌈💖

📦 where this page comes from