iort_dma_get_ranges(9)
π iort_dma_get_ranges(9) β Kernel API Manual, but make it cute β¨
okay so bestie, this is iort_dma_get_ranges(9) from the Kernel API Manual, and it is literally here to look up the DMA addressing limit for the device. That's the whole main-character assignment. π
πΈ NAME πΈ
iort_dma_get_ranges β Look up DMA addressing limit for the device. Periodt. π
π SYNOPSIS π
The signature is giving "short, iconic, don't touch the spacing":
int iort_dma_get_ranges (struct device *dev , u64 *limit );
π¦ ARGUMENTS π¦
devβ device to lookup. Like, the device you're looking up, bestie. πlimitβ DMA limit result pointer. This is the pointer where the DMA limit result goes. π«Ά
β RETURN β
Returns 0 on success, an error otherwise. No extra lore β that is the whole vibe check. π
π SEE ALSO π
Kernel file: ./drivers/acpi/arm64/iort.c β and the whole squad is right here, no cap:
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_add_platform_device(9)
xoxo, your fav kernel bestie π«Ά β source/version: ./drivers/acpi/arm64 Β· date: October 2026 Β· manual: iort_dma_get_ranges(9) π
π¦ 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