omap_iommu_runtime_resume(9)

📦 version 7.3.1, in nixpkgs unstable

💅 omap_iommu_runtime_resume(9) ✨ <small>(Kernel API Manual, bestie)</small>

okay so we're in the Kernel API Manual today and this one is genuinely iconic — meet omap_iommu_runtime_resume, the function that wakes an IOMMU device up and gets it ready to slay 🫶

🌸 NAME 🌸

omap_iommu_runtime_resume — enable an iommu device 💖

🦋 SYNOPSIS 🦋

int omap_iommu_runtime_resume (struct device *dev );

🎀 ARGUMENTS 🎀

  • dev — the iommu device itself, the main character of this whole situation 👑

✨ DESCRIPTION ✨

so like, this function does everything you need to actually enable an IOMMU device, no cap. it's the glow-up routine 💅

it handles the vibes in two separate scenarios:

  • when you're initially attaching to a client device (first-time meet-cute 🥺)
  • when the device is resuming, whether that's a system resume or a runtime resume (waking up from a nap 😴✨)

and what does "doing everything" actually mean? it includes:

  • programming all the appropriate IOMMU registers 🔥 — yes, all of them, it's giving thorough
  • managing the associated omap_hwmod's state — keeping that thing in check, fr fr
  • managing the device's reset line — the reset line is lowkey the whole plot

oh and one more thing bestie: if it's resuming after a suspend, the function also restores any locked TLBs. so those locked entries you left behind? restored. periodt. 💀

💖 SEE ALSO 💖

the kernel file ./drivers/iommu/omap-iommu.c is the mothership 🏠 and here's the whole friend group, all of them (9):

ngl if you're messing with IOMMU registers, read the whole squad above first. iykyk 💜

alright bestie that's the page 🫶 this one dropped from ./drivers/iommu back in October 2026, and honestly? she ate. go enable that IOMMU device, you've got this 👑💖

📦 where this page comes from