of_msi_map_g...evice_domain(9)

💅 of_msi_map_get_device_domain(9)

okay so bestie, this one's straight out of the Kernel API Manual ✨ and it's giving "short but iconic" — like a two-line text from your smartest friend. no cap, it's tiny, but it matters 🎀

---

🌸 NAME 🌸

of_msi_map_get_device_domain — it literally uses msi-map to find the relevant MSI domain. that's the whole assignment. periodt. 👑

✨ SYNOPSIS ✨

struct irq_domain * of_msi_map_get_device_domain (struct device *dev ,
u32 id , u32 bus_token );

look at that signature. struct irq_domain * coming back at you, three args going in. chef's kiss 🔥

💖 ARGUMENTS 💖

• dev — the device you're doing the mapping for. like, the main character of this whole operation 🫶
• id — the Device ID. yes bestie, the ID.
• bus_token — the Bus token. short name, big job ✨

🦋 DESCRIPTION 🦋

so here's the vibe: it walks up the device hierarchy 🔥 looking for devices that have an "msi-map" property. that's it. that's the tea. it goes up, it checks, it finds the ones with the property. iykyk 💜

🌈 RETURN 🌈

the MSI domain for this device — or NULL on failure 😭 so like, check your return value, bestie. don't get caught out there with a NULL and no plan 🙈

👑 SEE ALSO 👑

the kernel file ./drivers/of/irq.c is where it lives, and here's the whole friend group — they all show up together, no skipping 🎀

• 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_get_domain(9)
• of_msi_configure(9)

---

ok so real talk: if it fails you get NULL, so please actually check. i'm not gonna watch you crash 💀

and that's the page, bestie!! 🦋 mwah 💋 — this lil beauty ships from ./drivers/of, dated October 2026, and it's filed under the Kernel API Manual in case you need to find it again 🌸💖