irq_domain_set_info(9)

📦 version 7.3.1, in nixpkgs unstable

💅 irq_domain_set_info(9) 💅

Okay bestie, welcome to the Kernel API Manual — yes, the manual name is literally Kernel API Manual, we're in the kernel club now 🎀. This page is about one very specific little function that sets up all the interrupt info for a virtual IRQ, and honestly? It's giving “one stop shop” energy ✨.

💖 NAME 💖

irq_domain_set_info — literally sets the complete data for a @virq in @domain 💅. That's the whole vibe. No cap.

✨ SYNOPSIS ✨

void irq_domain_set_info (struct irq_domain *domain , unsigned int virq
, irq_hw_number_t hwirq , const struct irq_chip *chip , void *chip_data
, irq_flow_handler_t handler , void *handler_data , const char
*handler_name );

Like, yes, it's a long signature — but she's iconic for it 👑.

🎀 ARGUMENTS 🎀

  • domain — the interrupt domain to match. Think of it as the group chat this IRQ belongs to 🫶.
  • virq — the IRQ number. The virtual one, bestie 💫.
  • hwirq — the hardware interrupt number. The original, the real one, the main character 🔥.
  • chip — the associated interrupt chip. The hardware bestie that handles the actual work 💅.
  • chip_data — the associated interrupt chip data. Extra lil’ context for the chip 🍓.
  • handler — the interrupt flow handler. The one who knows the flow, fr fr 🌊.
  • handler_data — the interrupt flow handler data. More context for the handler, because she needs her details too 🧚.
  • handler_name — the interrupt handler name. Name her, don't leave her unnamed 😭.

🦋 SEE ALSO 🦋

Kernel file: ./kernel/irq/irqdomain.c — that's the home base for all this IRQ domain lore, iykyk 🏡.

That's the whole friend group right there 🌈. Go read them, bestie — they all ate 💖.

So yeah, that's the page 🫶. It came from the source/version thingy ./kernel/irq, dated October 2026, and it's filed under irq_domain_set_info(9) — periodt 💅✨.

📦 where this page comes from