iort_msi_xlate(9)

🌸 NAME 🌸

Bestie, meet iort_msi_xlate(9) from the Kernel API Manual ✨ Its whole thing is literally this: map a MSI input ID for a device. That's the assignment, and it ate 💅

✨ SYNOPSIS ✨

u32 iort_msi_xlate (struct device *dev , u32 input_id , struct fwnode_handle **fwnode );

🎀 ARGUMENTS 🎀

• dev — the device for which the mapping is to be done. Main character device energy 🫶
• input_id — the device input ID.
• fwnode — pointer to store the fwnode. Yes bestie, it's holding space for that fwnode 🌸

🔥 RETURN 🔥

You get the mapped MSI ID on success, and you get the input_id otherwise. No cap 💀 On success, the fwnode pointer is initialized to the MSI controller fwnode handle. Slay 💖

🦋 SEE ALSO 🦋

• Kernel file: ./drivers/acpi/arm64/iort.c
• iort_set_fwnode(9)
• 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_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)

Source/version footer vibes: ./drivers/acpi/arm64 · date: October 2026 · manual: iort_msi_xlate(9). Okay bye bestie, go map those MSI IDs and eat 💅🍓