omap_iommu_domain_activate(9)

🦋 omap_iommu_domain_activate(9) 🦋

okay bestie, welcome to the Kernel API Manual — this page is about omap_iommu_domain_activate, and it’s lowkey a whole runtime-resume situation. 🫶

💖 NAME 💖

omap_iommu_domain_activate — activate attached iommu devices ✨

🌸 SYNOPSIS 🌸

int omap_iommu_domain_activate (struct iommu_domain *domain );

✨ ARGUMENTS ✨

• domain — the iommu domain attached to the target iommu device. That’s the one getting activated, no cap. 🎀

🦋 DESCRIPTION 🦋

okay so here’s the tea: this API lets the client devices of IOMMU devices resume the IOMMUs they control at runtime, and they gotta do that before they can resume operations. literally the “wake up babe, we’re resuming” moment. 💅

System Resume will leverage the PM driver late callbacks. that’s the assigned main character energy for the resume flow, fr fr. 🔥

🎀 SEE ALSO 🎀

• Kernel file ./drivers/iommu/omap-iommu.c to to_omap_domain(9)
• omap_iommu_save_ctx(9)
• omap_iommu_restore_ctx(9)
• load_iotlb_entry(9)
• flush_iotlb_page(9)
• flush_iotlb_all(9)
• omap_iopgtable_store_entry(9)
• iopgtable_lookup_entry(9)
• iopgtable_clear_entry(9)
• omap_iommu_attach(9)
• omap_iommu_detach(9)
• omap_iommu_domain_deactivate(9)
• omap_iommu_runtime_suspend(9)
• omap_iommu_runtime_resume(9)
• omap_iommu_prepare(9)

okay bye bestie — source: ./drivers/iommu, date: October 2026, and it’s still the Kernel API Manual. slay 💅✨