devm_irq_domain_instantiate(9)

💅 NAME 💅

okay so bestie, welcome to the devm_irq_domain_instantiate(9) page — this is the Kernel API Manual and it's literally about instantiating a new irq domain data for a managed device. yes that's the whole vibe. devm-coded, managed, gorgeous. ✨

---

🎀 SYNOPSIS 🎀

like here's the signature, copy it exactly, no cap:

struct irq_domain * devm_irq_domain_instantiate (struct device *dev ,
const struct irq_domain_info *info );

---

🌸 ARGUMENTS 🌸

two args, both iconic, both mandatory:

• dev — the Device you're instantiating the domain for. it's giving "who is this for" energy 🫶
• info — the Domain information pointer, and it's pointing at the information for this domain. so like, the lore. the details. the whole situation. 💅

---

⭐ RETURN ⭐

you get back a pointer to the instantiated irq domain — slay — or an ERR_PTR value 😭. so yeah, check it, don't just rawdog it into a dereference. fr fr.

bestie pls remember: ERR_PTR is a real possible return, it's not a drill, vibe check your pointers 💀

---

🦋 SEE ALSO 🦋

the whole friend group, all of them, in order, no skips:

• Kernel file ./kernel/irq/devres.c
• devm_request_threaded_irq(9)
• devm_request_any_context_irq(9)
• devm_free_irq(9)
• __devm_irq_alloc_descs(9)
• devm_irq_alloc_generic_chip(9)
• devm_irq_setup_generic_chip(9)

---

and that's the page!! mwah 💖

cute little sign-off for the girlies: this one lives in ./kernel/irq, dated October 2026, and it's devm_irq_domain_instantiate(9) all the way down. periodt. 👑🌈