irq_domain_a..._irqs_parent(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… irq_domain_alloc_irqs_parent β€” NAME ✨

okay so bestie, this is a page from the Kernel API Manual, and the function is irq_domain_alloc_irqs_parent β€” it allocates interrupts from the parent domain. that's the whole vibe. your domain's parent has the goods, and this function goes and gets 'em 🫢


🌸 SYNOPSIS 🌸

int irq_domain_alloc_irqs_parent (struct irq_domain *domain , unsigned
int irq_base , unsigned int nr_irqs , void *arg );

like, look at her. four params, returns an int, main character energy fr fr πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • domain β€” the domain below which interrupts must be allocated. so she's the one sitting under the parent, and everything gets allocated underneath her. queen of hierarchy πŸ‘‘
  • irq_base β€” the base IRQ number. the starting point, the origin story, the place where the numbering begins ✨
  • nr_irqs β€” number of IRQs to allocate. how many we're grabbing. no cap, you gotta tell her πŸ™ˆ
  • arg β€” allocation data, and it's arch/domain specific β€” meaning it's giving "you know your own architecture best, i don't know her" πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹

so there's a whole friend group here, and they all live in the kernel file ./kernel/irq/irqdomain.c β€” go say hi to the gc:


okay that's the whole page bestie, ily, go allocate some interrupts responsibly πŸ§šπŸ’–

this lil cutie lives in ./kernel/irq, and the manual page is dated October 2026 β€” so jot that down, it's irq_domain_a..._irqs_parent(9), periodt. πŸ’œ
πŸ“¦ where this page comes from