ccio_get_iommu(9)

💅 ccio_get_iommu

ok so this is a page from the Kernel API Manual, and bestie, it's literally just one (1) function that answers the question "which iommu is this device's problem?" 🎀

✨ NAME ✨

ccio_get_iommu — find the iommu which controls this device 🦋

🌸 SYNOPSIS 🌸

void * ccio_get_iommu (const struct parisc_device *dev );

🫶 ARGUMENTS 🫶

• dev — the parisc device. that's it, that's the whole argument. she's low maintenance 💅

🔥 DESCRIPTION 🔥

okay so picture this: this function goes rummaging through all the registered IOMMU's 📚 and then hands you back the appropriate IOMMU for the device — and the way it decides is literally based on the device's hardware path. no cap, that's the whole vibe check. iconic, honestly ✨

👑 SEE ALSO 👑

kernel file ./drivers/parisc/ccio-dma.c 🍓 and bringing the whole friend group:

• ccio_alloc_range(9)
• ccio_free_range(9)
• ccio_io_pdir_entry(9)
• ccio_clear_io_tlb(9)
• ccio_mark_invalid(9)
• ccio_dma_supported(9)
• ccio_map_single(9)
• ccio_unmap_phys(9)
• ccio_alloc(9)
• ccio_free(9)
• ccio_map_sg(9)
• ccio_unmap_sg(9)
• ccio_find_ioc(9)
• ccio_ioc_init(9)
• ccio_probe(9)
• ccio_init(9)

ok that's the whole page, luv u, bye 💖 this cutie came out of ./drivers/parisc, dated October 2026, and it's filed under ccio_get_iommu(9) — stream it, rate it five stars ⭐ mwah 😭💜