ti_sci_inta_...c_parent_irq(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so bestie, this is ti_sci_inta_alloc_parent_irq β€” and what it does is, like, allocate a parent irq to the Interrupt aggregator. that's the whole vibe. very demure, very interrupt-y πŸ’…

and hey, just so we're clear on where we're at: this is the Kernel API Manual section, so we're deep in kernel-land rn 🫢


✨ SYNOPSIS ✨

struct ti_sci_inta_vint_desc * ti_sci_inta_alloc_parent_irq (struct irq_domain *domain );

like, that's the whole signature, no notes πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • domain β€” the IRQ domain that corresponds to the Interrupt Aggregator. that's it, that's the one argument, she's lowkey the main character here πŸ¦‹

πŸ’– DESCRIPTION πŸ’–

so the rundown is: it returns 0 if everything went well, otherwise it hands you back the corresponding error value. no cap, that's literally what the page says β€” success means 0, and anything else means an error is being reported 😭

fr fr, that's the entire description. sometimes the kernel is a woman of few words πŸ™ˆ

πŸ”₯ SEE ALSO πŸ”₯

okay this list is long and honestly iconic, so let's get into it. first up, the kernel file where all of this lives:

./drivers/irqchip/irq-ti-sci-inta.c

and then the whole friend group of related pages β€” go read these if you want the full lore:

like, that's an entire ensemble cast and every single one of them slayed in their own way, ngl 🧚


mwah, that's a wrap πŸ’œ this little page came from the ./drivers/irqchip corner of the universe, dated October 2026, and it answers to the name ti_sci_inta_...c_parent_irq(9) β€” periodt, go read your interrupts, bestie 🌈⭐

πŸ“¦ where this page comes from