pcim_iomap_range(9)

💅 pcim_iomap_range(9) 💅

okay so bestie, this is a page straight out of the Kernel API Manual — yes, the actual kernel manual, and yes, we're gonna make it make sense 🫶

---

✨ NAME ✨

pcim_iomap_range — creates a ranged __iomap mapping, like, inside a PCI BAR. that's the whole vibe 💖

---

🌸 SYNOPSIS 🌸

void __iomem * pcim_iomap_range (struct pci_dev *pdev , int bar ,
unsigned long offset , unsigned long len );

---

🎀 ARGUMENTS 🎀

• pdev — the PCI device you're mapping IO resources for. the main character, basically 👑
• bar — the index of the BAR. just the number index, nothing deeper, don't overthink it 💅
• offset — how far from the begin of the BAR you're starting. your little starting point ✨
• len — length in bytes for the mapping. how much you're taking, in bytes, no cap 📏

---

🦋 RETURN 🦋

a __iomem pointer on success 💖 — and on failure you get an IOMEM_ERR_PTR 😭 (so like, check that bad boy, fr fr).

---

🌈 DESCRIPTION 🌈

so it creates a new IO-Mapping within the specified bar, ranging from offset to offset + len. cute, tidy, exactly what it says 🎯

and here's the slay part: the mapping will automatically get unmapped on driver detach ✨ like it handles its own cleanup, icon behaviour honestly.

but lowkey listen — if you desired, you can release manually, and only with pcim_iounmap. that's the one. don't get creative 🙈

---

⭐ SEE ALSO ⭐

• the kernel file ./drivers/pci/devres.c — that's where the lore lives 📖
• devm_pci_remap_iospace(9)
• 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)

like, the whole friend group, iykyk 💜

---

and that's the page!! brought to you by ./drivers/pci, dated October 2026 🌸🦋 — mwah, go map responsibly, bestie 💅✨