ti_sci_intr_...c_parent_irq(9)

🌸 ti_sci_intr_alloc_parent_irq — bestie edition 🌸

okay so this is from the Kernel API Manual, page ti_sci_intr_...c_parent_irq(9), and honestly? it's a little baddie. let's get into it 💅

---

✨ NAME ✨

ti_sci_intr_alloc_parent_irq — Allocate parent IRQ. that's it. that's the whole vibe. it goes and gets you a parent IRQ 🎀

---

🦋 SYNOPSIS 🦋

int ti_sci_intr_alloc_parent_irq (struct irq_domain *domain , unsigned
int virq , u32 hwirq , u32 hwirq_type );

like, literally just call it with those four things and it hands you back an int. iconic signature ngl ✨

---

💖 ARGUMENTS 💖

• domain — Pointer to the interrupt router IRQ domain. this is the main character domain, the interrupt router one, and you're passing a pointer to it 🫶
• virq — Corresponding Linux virtual IRQ number. yes bestie, the virtual one, the Linux-side number ✨
• hwirq — Corresponding hwirq for the IRQ within this IRQ domain. the hardware number, scoped to this IRQ domain, no cap 🔥
• hwirq_type — Corresponding hwirq trigger type for the IRQ within this IRQ domain. also scoped to this domain — it's the trigger type, so like, how it fires 💫

---

🌈 DESCRIPTION 🌈

so what does it actually do?? it returns the intr output irq if all went well 💖 — and if it didn't go well, you get the appropriate error pointer instead 😭. that's the whole deal, fr fr. good vibes or an error pointer, there is no in-between 🦋

---

👑 SEE ALSO 👑

peep the kernel file ./drivers/irqchip/irq-ti-sci-intr.c and also these lil faves:

• struct ti_sci_intr_irq_domain(9)
• ti_sci_intr_irq_domain_translate(9)
• ti_sci_intr_xlate_irq(9)
• ti_sci_intr_irq_domain_free(9)
• ti_sci_intr_irq_domain_alloc(9)

all the siblings, all slaying in the same file 💅✨

---

oh and before you go — this one's living in ./drivers/irqchip, dated October 2026, and the page is ti_sci_intr_...c_parent_irq(9). mwah, go read the source bestie 🍓💜