iort_find_domain_token(9)
bestie, welcome to the iort_find_domain_token(9) page from the Kernel API Manual β itβs a tiny little lookup era, and weβre gonna get through it together πβ¨
πΈ NAME πΈ
iort_find_domain_token β find the domain token based on the given ITS ID. Thatβs the whole vibe: you hand it an ITS ID, it goes looking π΅οΈββοΈπ
β¨ SYNOPSIS β¨
struct fwnode_handle * iort_find_domain_token (int trans_id );
π ARGUMENTS π
trans_idβ the ITS ID. Thatβs the thing youβre using for the lookup, periodt π
π¦ RETURN π¦
When it finds the domain token on the list, it returns that domain token. Otherwise? NULL. Thatβs it, thatβs the whole return journey ππ«Ά
π₯ SEE ALSO π₯
Kernel file ./drivers/acpi/arm64/iort.c, plus the whole function friend group β no cap, every single one:
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_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)
okay bestie, cute sign-off time: this page lives in ./drivers/acpi/arm64, itβs dated October 2026, and itβs literally the iort_find_domain_token(9) manual page β slay, go find those tokens ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms