arm_iommu_attach_device(9)

💖 arm_iommu_attach_device(9) 💖

okay so this is a page from the Kernel API Manual — yes, the kernel manual, we're doing Big Kernel Energy today bestie, buckle up 🎀

---

✨ NAME ✨

arm_iommu_attach_device — ngl the original page leaves the description blank, so there's literally no one-liner here. The name is the whole vibe. It's the attach function, and the deets are all down in DESCRIPTION 🫶

---

🌸 SYNOPSIS 🌸

int arm_iommu_attach_device (struct device *dev , struct
       dma_iommu_mapping *mapping );

---

🦋 ARGUMENTS 🦋

• dev — a valid struct device pointer, okurrr. Must be valid, that's the whole requirement, don't come at it with garbage 💅
• mapping — the io address space mapping structure. And where do you get one of those? It's the thing returned from arm_iommu_create_mapping, so go make one first, bestie, no shortcuts 😌

---

🌈 DESCRIPTION 🌈

So what does it actually do? It attaches the specified io address space mapping to the device you handed it. Simple, iconic, main character energy ✨

The way it works: it replaces the dma operations (that's the dma_map_ops pointer, iykyk) with the IOMMU aware version. So your device stops doing plain dma and starts doing IOMMU-flavoured dma. A total glow-up 🔥

💜 And here's the cute part — more than one client might be attached to the same io address space mapping. Sharing is caring, fr fr.

---

⭐ SEE ALSO ⭐

• Kernel file ./arch/arm/mm/dma-mapping.c 👑
• arm_iommu_map_sg(9)
• arm_iommu_unmap_sg(9)
• arm_iommu_sync_sg_for_cpu(9)
• arm_iommu_sync_sg_for_device(9)
• arm_iommu_map_phys(9)
• arm_iommu_create_mapping(9)
• arm_iommu_detach_device(9)

---

and that's the page, bestie 🍓 this lil gem lives over in ./arch/arm/mm and it's dated October 2026 — yeah, we're reading from the future, don't question it 💀✨ go forth and attach responsibly 🧚💖