STRUCT TI_SCI_INTR_IRQ_DOMAIN(9)

💅 struct ti_sci_intr_irq_domain — NAME, bestie, NAME

okay so this page is literally about struct ti_sci_intr_irq_domain — a structure that represents a TISCI-based Interrupt Router IRQ domain. that's it, that's the whole vibe. it's the little data bundle that holds everything the kernel needs to know about one of these interrupt routers 🎀

✨ SYNOPSIS ✨

here's the whole shape of it, no cap, copy this exactly:

struct ti_sci_intr_irq_domain {
    const struct ti_sci_handle *sci;
    struct ti_sci_resource *out_irqs;
    struct device *dev;
    u32 ti_sci_id;
    u32 type;
 };

yeah she's small but she's doing SO much 💅 every single field is important, so let's walk through them one by one 🫶

🦋 Members 🦋

okay so the members, in order, zero skipping:

• sci — a pointer to the TISCI handle. this is your main character pointer, the connection to TISCI itself ✨
• out_irqs — a TISCI resource pointer that represents the INTR irqs. like, the actual interrupt resources this domain is working with 💖
• dev — a struct device pointer. the device that owns this whole situation 🎀
• ti_sci_id — the TI-SCI device identifier. it's a u32, and it's the ID that TISCI uses to know which device we're talking about 👑
• type — specifies the trigger type supported by this Interrupt Router. also a u32. so whatever triggers this router supports, that's what lives here 🌸

ngl these are all just pointers and u32s, but together they're the entire identity of an interrupt router domain. iykyk 😭

🌈 SEE ALSO 🌈

the related reading, because bestie you will want to see also:

• Kernel file ./drivers/irqchip/irq-ti-sci-intr.c
• ti_sci_intr_irq_domain_translate(9)
• ti_sci_intr_xlate_irq(9)
• ti_sci_intr_irq_domain_free(9)
• ti_sci_intr_alloc_parent_irq(9)
• ti_sci_intr_irq_domain_alloc(9)

and that's the whole page, bestie 💜 no drama, no hidden tricks, just a clean little struct living its best life over in ./drivers/irqchip. this gem is from the Kernel API Manual, dated October 2026 — slay, iconic, periodt 🧚⭐