devm_pci_remap_iospace(9)

💅 devm_pci_remap_iospace(9)

okay bestie, so this one lives in the Kernel API Manual and it's literally the managed version of pci_remap_iospace() — like, it handles the cleanup for you so you don't have to 😭✨

---

🌸 SYNOPSIS 🌸

int devm_pci_remap_iospace (struct device *dev , const struct resource
*res , phys_addr_t phys_addr );

that's the whole vibe. returns an int, takes three things, we move 💅

---

🎀 ARGUMENTS 🎀

• dev — the generic device you're remapping the IO address for 🫶
• res — the resource that describes the I/O space, iykyk
• phys_addr — the physical address of the range you wanna map, no cap

---

✨ DESCRIPTION ✨

it's the managed pci_remap_iospace. the map gets automatically unmapped when the driver detaches — so you literally don't have to lift a finger, it's giving main character energy with a built-in cleanup crew 👑

---

🦋 SEE ALSO 🦋

kernel file ./drivers/pci/devres.c, plus these iconic siblings:

• devm_pci_remap_cfgspace(9)
• devm_pci_remap_cfg_resource(9)
• pcim_set_mwi(9)
• pcim_intx(9)
• pcim_enable_device(9)
• pcim_pin_device(9)
• pcim_iomap_table(9)
• pcim_iomap(9)
• pcim_iounmap(9)
• pcim_iomap_region(9)
• pcim_iounmap_region(9)
• pcim_iomap_regions(9)
• pcim_request_region(9)
• pcim_release_region(9)
• pcim_release_all_regions(9)
• pcim_request_all_regions(9)
• pcim_iomap_range(9)

---

ngl this whole family is a whole friend group and they all show up to the function-call party together 🫶

---

k that's it, that's the page 💜 this one ships out of ./drivers/pci and it's dated October 2026 — slay, see you in the next manpage bestie 🎀✨