iort_set_fwnode(9)

✨ iort_set_fwnode(9) ✨

okay so bestie, welcome to the Kernel API Manual 💖 this one's called iort_set_fwnode, and it's literally the glow-up moment where an IORT thing gets its very own fwnode bestie. 🎀

---

🌸 NAME 🌸

iort_set_fwnode — create an iort_fwnode and use it to register iommu data in the iort_fwnode_list 🦋

like yes, that's the whole job. make the thing, then use the thing to get your iommu data on the list. iconic behavior tbh.

---

🧚 SYNOPSIS 🧚

int iort_set_fwnode (struct acpi_iort_node *iort_node , struct fwnode_handle *fwnode );

---

💅 ARGUMENTS 💅

• iort_node — the IORT table node that's associated with the IOMMU. that's its whole personality, it's the table node. 🫶
• fwnode — the fwnode that's associated with the IORT node. they're a matching set, no cap. ✨

---

👑 RETURN 👑

Returns 0 on success, and <0 on failure 😭 — so bestie, 0 is the slay outcome, anything negative is the vibe check failing. 💀

---

🌈 SEE ALSO 🌈

kernel file ./drivers/acpi/arm64/iort.c (the source of truth, the main character 🎀), plus the whole friend group:

• iort_get_fwnode(9)
• iort_delete_fwnode(9)
• iort_get_iort_node(9)
• iort_register_domain_token(9)
• iort_deregister_domain_token(9)
• iort_find_domain_token(9)
• iort_msi_map_id(9)
• iort_msi_xlate(9)
• iort_pmsi_get_msi_info(9)
• iort_dev_find_its_id(9)
• iort_get_device_domain(9)
• iort_get_platform_device_domain(9)
• iort_iommu_get_resv_regions(9)
• iort_get_rmr_sids(9)
• iort_put_rmr_sids(9)
• iort_iommu_configure_id(9)
• iort_dma_get_ranges(9)
• iort_add_platform_device(9)

---

💖 reminder bestie: 0 = success, <0 = failure. don't forget to check the return value, that's the bare minimum. 😌

---

so yeah, that's the page!! brought to you straight from ./drivers/acpi/arm64, dated October 2026, and yeah the footer says iort_set_fwnode(9) because it's that girl. 🌟 mwah, go call it responsibly 💜