devm_ioport_unmap(9)

💅 devm_ioport_unmap(9) — like, the managed unmap, bestie

okay so welcome to the Kernel API Manual ✨ this one's short and sweet and honestly kind of a vibe. it's devm_ioport_unmap, and yes the 9 means it's a kernel function page, iykyk 🎀

---

✨ NAME ✨

devm_ioport_unmap — the managed version of ioport_unmap(). that's it, that's the whole name 🫶

---

🌸 SYNOPSIS 🌸

void devm_ioport_unmap (struct device *dev , void __iomem *addr );

literally two arguments, no return value, no drama. she just unmaps and leaves 💅

---

🦋 ARGUMENTS 🦋

• dev — the generic device you're unmapping for. the whole "managed" thing hinges on this baby, so don't go handing over some random pointer 🙈
• addr — the address to unmap. the actual thing getting cleaned up ⭐

---

👑 DESCRIPTION 👑

so devm_ioport_unmap is a managed ioport_unmap — the devres machinery handles the cleanup timing for you, which is the entire point of the devm_ prefix ✨

⚠️ okay bestie, important: addr must have been mapped using devm_ioport_map. that's not a suggestion, that's the contract. no cap, fr fr. don't be out here unmapping addresses that came from somewhere else 😭

---

🍓 SEE ALSO 🍓

the kernel file ./lib/devres.c and her whole friend group:

• devm_ioremap(9)
• devm_ioremap_uc(9)
• devm_ioremap_wc(9)
• devm_iounmap(9)
• devm_ioremap_resource(9)
• devm_ioremap_resource_wc(9)
• devm_ioport_map(9)
• devm_arch_phys_wc_add(9)
• devm_arch_io_reserve_memtype_wc(9)

like, the entire devm_ cinematic universe 🌈 go read devm_ioport_map(9) next if you want the origin story 💖

---

and that's the page!! signing off from the ./lib source, October 2026, in the Kernel API Manual — mwah, slay, go unmap responsibly 💜🧚‍♀️