ti_sci_inta...st_resources(9)

🌸 NAME 🌸

okay so bestie, this is the Kernel API Manual page for ti_sci_inta_request_resources, and it is literally about allocating resources for an input irq 💅. The page title shows up as the truncated ti_sci_inta...st_resources(9) — slay, we move 🫶.

✨ SYNOPSIS ✨

the whole vibe check is this signature:

int ti_sci_inta_request_resources (struct irq_data *data );

🎀 ARGUMENTS 🎀

• data — pointer to the corresponding irq_data. that's the whole arg list, iconic 💖

💅 NOTE 💅

okay so this is the core api where the actual allocation happens for input hwirq ✨. This allocation involves creating a parent irq for vint. If this is done in irq_domain_ops.alloc, then a deadlock is reached for allocation 💀 — not the cute kind, bestie. So this allocation is being done in request_resources instead. periodt.

💖 RETURN 💖

0 if all went well, else the corresponding error. simple as that 🍓

🦋 SEE ALSO 🦋

Kernel file: ./drivers/irqchip/irq-ti-sci-inta.c

• struct ti_sci_inta_event_desc(9)
• struct ti_sci_inta_vint_desc(9)
• struct ti_sci_inta_irq_domain(9)
• ti_sci_inta_irq_handler(9)
• ti_sci_inta_xlate_irq(9)
• ti_sci_inta_alloc_parent_irq(9)
• ti_sci_inta_alloc_event(9)
• ti_sci_inta_alloc_irq(9)
• ti_sci_inta_free_parent_irq(9)
• ti_sci_inta_free_irq(9)
• ti_sci_inta_release_resources(9)
• ti_sci_inta_manage_event(9)
• ti_sci_inta_mask_irq(9)
• ti_sci_inta_unmask_irq(9)
• ti_sci_inta_ack_irq(9)
• ti_sci_inta_set_type(9)
• ti_sci_inta_irq_domain_free(9)
• ti_sci_inta_irq_domain_alloc(9)

and that's the whole page, bestie 💜 — this one comes from source path ./drivers/irqchip, dated October 2026, and the page is ti_sci_inta...st_resources(9). slay ✨