__irq_domain_alloc_fwnode(9)

📦 version 7.3.1, in nixpkgs unstable

✨ __irq_domain_alloc_fwnode(9) ✨

okay so welcome to the Kernel API Manual bestie 💖 this one's all about __irq_domain_alloc_fwnode — the lil' allocation helper for irq domain fwnodes. yes it's niche. yes it's iconic. let's go 🌸

🎀 NAME 🎀

__irq_domain_alloc_fwnode — literally allocate a fwnode_handle that's suitable for identifying an irq domain 🦋

🌈 SYNOPSIS 🌈

struct fwnode_handle * __irq_domain_alloc_fwnode (unsigned int type ,
      int id , const char *name , phys_addr_t *pa , struct fwnode_handle
      *parent );

💜 ARGUMENTS 💜

  • type — the type of irqchip_fwnode. peep linux/irqdomain.h for the deets 👀
  • id — an optional user-provided id, but only if name != NULL 🫶
  • name — an optional user-provided domain name, no pressure ✨
  • pa — an optional user-provided physical address 📍
  • parent — an optional parent fwnode_handle 👑

🦋 DESCRIPTION 🦋

So what it does is: allocate a struct irqchip_fwid, and hand you back a pointer to the embedded fwnode_handle (or NULL on failure, bestie — that's the flop era case 😭).

🔥 NOTE 🔥

The types IRQCHIP_FWNODE_NAMED and IRQCHIP_FWNODE_NAMED_ID are solely there to transport name information to the irqdomain creation code. the node is not stored, periodt 💅 for other types the pointer is kept in the irq domain struct.

fr fr, don't assume the node gets stashed away for those two named types — it doesn't 🙈

👑 SEE ALSO 👑

kernel file ./kernel/irq/irqdomain.c 🌟 and also these iconic friends:

mwah 💋 that's the whole page — sourced from ./kernel/irq, dated October 2026, and yeah it's the __irq_domain_alloc_fwnode(9) manual. go be a main character in your irq domain now 🧚💜

📦 where this page comes from