iort_add_platform_device(9)

🌸 NAME 🌸

iort_add_platform_device — Allocate a platform device for IORT node. This one's from the Kernel API Manual, and yes bestie it's giving kernel-internals realness 💅✨.

🎀 SYNOPSIS 🎀

okay so the exact signature is literally this, no cap:

int iort_add_platform_device (struct acpi_iort_node *node , const struct
       iort_dev_config *ops );

🦋 ARGUMENTS 🦋

Two pointers, two jobs. Iconic behavior fr fr 💖.

• node — Pointer to device ACPI IORT node. That's the ACPI IORT node for the device 🌈.
• ops — Pointer to IORT device config struct. That's the config struct for the IORT device 🎀.

⭐ RETURN ⭐

0 on success, <0 failure. That's the whole vibe check — success is 0, and anything below that is a fail 💀😭.

💖 SEE ALSO 💖

Kernel file ./drivers/acpi/arm64/iort.c — and look at this whole friend group, bestie:

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

okay that's the page, bestie — source/version: ./drivers/acpi/arm64; date: October 2026. mwah 💋✨