STRUCT TI_SCI_INTA_IRQ_DOMAIN(9)

📦 version 7.3.1, in nixpkgs unstable

💅 struct ti_sci_inta_irq_domain — NAME ✨

okay so bestie, this is the page for struct ti_sci_inta_irq_domain in the Kernel API Manual — and it's literally the structure that represents a TISCI based Interrupt Aggregator IRQ domain. that's the whole vibe, no cap. 🎀

🦋 SYNOPSIS

struct ti_sci_inta_irq_domain {
    const struct ti_sci_handle *sci;
    struct ti_sci_resource *vint;
    struct ti_sci_resource *global_event;
    struct list_head vint_list;
    struct mutex vint_mutex;
    void __iomem *base;
    struct platform_device *pdev;
    u32 ti_sci_id;
    int unmapped_cnt;
    u16 *unmapped_dev_ids;
 };

like, that's the whole struct, copy-pasted straight from the source, don't @ me 💖

🌸 Members ✨

okay let's go through every single field because we do NOT skip details in this house 👑

  • sci — pointer to the TISCI handle. your main character pointer, fr.
  • vint — TISCI resource pointer representing IA interrupts. that's the interrupt-aggregator interrupt resource, iykyk.
  • global_event — TISCI resource pointer representing global events. yes it's a whole separate resource pointer, slay.
  • vint_list — list of the vints that are active in the system. 📋
  • vint_mutex — mutex that protects vint_list. do NOT touch that list without it, bestie, that's the whole point 🙈
  • base — base address of the memory mapped IO registers. void __iomem *, iconic.
  • pdev — pointer to platform device. yes queen, the platform device itself.
  • ti_sci_id — TI-SCI device identifier. a u32, obviously.
  • unmapped_cnt — the number of unmapped_dev_ids entries. just a count, int, living its life.
  • unmapped_dev_ids — pointer to an array of TI-SCI device identifiers of unmapped event sources. ok so this one needs the full explanation and it's genuinely so good:

Unmapped Events are not part of the Global Event Map, and they get converted to a Global event within INTA so they can be received by that same INTA and generate an interrupt. ✨

And here's the crucial part: in case an interrupt request comes for a device that's generating an Unmapped Event, we must use the INTA's TI-SCI device identifier in place of the source device identifier — so that sysfw knows where it has to program the Global Event number. that's the whole reason this array exists, bestie, don't forget it 🫶

🌈 SEE ALSO

kernel file ./drivers/irqchip/irq-ti-sci-inta.c plus all these beauties:

like, read them, they're all connected, it's giving lore 🤓💜

ok that's the whole page, nothing skipped, every member accounted for. go forth and understand your interrupt aggregator domain, bestie 💅✨

and that's a wrap! 🎀 this came out of the Kernel API Manual, sourced from ./drivers/irqchip, dated October 2026 — struct ti_s...a_irq_domain(9), mwah, periodt 💖🦋🌸

📦 where this page comes from