__irq_resolve_mapping(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __irq_resolve_mapping ✨

okay so this is the __irq_resolve_mapping(9) page from the Kernel API Manual, and bestie, it's literally a whole thing about finding your linux irq from a hw irq number. it's giving "short but iconic" β€” let's get into it 🫢


🌸 NAME 🌸

__irq_resolve_mapping β€” Find a linux irq from a hw irq number.

like, that's the whole gig. you got a hardware number, you want the linux one. slay.


✨ SYNOPSIS ✨

struct irq_desc * __irq_resolve_mapping (struct irq_domain *domain ,
irq_hw_number_t hwirq , unsigned int *irq );

πŸŽ€ ARGUMENTS πŸŽ€

  • domain β€” the domain owning this hardware interrupt, i.e. the main character that's in charge of this hw interrupt πŸ’–
  • hwirq β€” the hardware irq number in that domain space, fr fr the raw one
  • irq β€” optional pointer to return the Linux irq if required β€” no cap, it's optional, so you can pass it or not, your call πŸ¦‹

πŸ¦‹ DESCRIPTION πŸ¦‹

Returns the interrupt descriptor. that's it, that's the sentence. periodt. πŸ’…

like, genuinely, it's just handing you back a struct irq_desc *. lowkey obsessed with how unbothered this description is.


🌈 SEE ALSO 🌈

the Kernel file ./kernel/irq/irqdomain.c and honestly a whole friend group of functions β€” here's the full squad, no one left behind πŸ‘‘


and that's the vibe check, bestie β€” this page is from ./kernel/irq, dated October 2026, and the whole thing is filed under __irq_resolve_mapping(9) in case you need to find it again πŸ’œ mwah, go resolve some mappings πŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from