of_msi_get_domain(9)

💅 of_msi_get_domain(9) 💅

okay so this is a page straight out of the Kernel API Manual, and it's literally about one tiny little function that goes looking for your MSI domain using msi-parent. stay with me bestie, it's shorter than you think 🫶

---

✨ NAME ✨

of_msi_get_domain — uses msi-parent to find the relevant MSI domain, no cap

---

🦋 SYNOPSIS 🦋

struct irq_domain * of_msi_get_domain (struct device *dev , const struct
       device_node *np , enum irq_domain_bus_token token );

like, it hands you back a struct irq_domain * and takes three lil arguments. that's the whole vibe ✨

---

🎀 ARGUMENTS 🎀

• dev — the device you're requesting the domain for, bestie. it's giving "who is this for" 🫶
• np — the device node for dev. the matching node, the other half, the pair 💖
• token — the bus type for this domain. yes it matters, it's the vibe check for which domain you get 🌸

---

💅 DESCRIPTION 💅

so what it does is parse the msi-parent property and return the corresponding MSI domain. that's it. that's the whole function. iconic, honestly 👑

---

⭐ RETURN ⭐

the MSI domain for this device — or NULL on failure, and we do NOT gatekeep that possibility 😭

---

🌈 SEE ALSO 🌈

the kernel file lives at ./drivers/of/irq.c, and here's the whole friend group of related pages, fr fr:

• irq_of_parse_and_map(9)
• of_irq_find_parent(9)
• of_irq_parse_raw(9)
• of_irq_parse_one(9)
• of_irq_to_resource(9)
• of_irq_get(9)
• of_irq_get_byname(9)
• of_irq_count(9)
• of_irq_to_resource_table(9)
• of_irq_init(9)
• of_msi_xlate(9)
• of_msi_map_get_device_domain(9)
• of_msi_configure(9)

---

ngl this one's a quick read — go touch some grass, then come back and read the whole of_irq_* family 💜

---

mwah 💋 that's a wrap! this lil page came from the source tree at ./drivers/of, dated October 2026, and it's still called of_msi_get_domain(9) — same name, same numbers, always 🧚‍♀️✨