iort_msi_map_id(9)

💖 NAME 💖

okay bestie, this is iort_msi_map_id(9) from the Kernel API Manual — and it does exactly what it says on the tin: Map a MSI input ID for a device ✨

🦋 SYNOPSIS 🦋

u32 iort_msi_map_id (struct device *dev , u32 input_id );

🎀 ARGUMENTS 🎀

• dev — the device where the mapping is gonna happen, bestie 💅
• input_id — the device input ID, periodt.

🌸 RETURN 🌸

on success you get the mapped MSI ID back ✨ otherwise you get the input ID back. no cap, that's the whole vibe check.

👑 SEE ALSO 👑

the kernel file is ./drivers/acpi/arm64/iort.c, and these icon references are all in the group chat too 🫶

• 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_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)

that's the whole page, bestie 💖 source/version is ./drivers/acpi/arm64, dated October 2026, and it's giving absolutely iconic kernel-manual energy 🌈👑🦋