devm_pci_remap_cfgspace(9)

✨ NAME ✨

devm_pci_remap_cfgspace — the managed pci_remap_cfgspace(), and yes bestie, it's giving "I clean up after myself" energy 💅

Okay so you're on the devm_pci_remap_cfgspace(9) page in the Kernel API Manual, and this is the device-managed remap situation. Grab your struct device * and let's get into it 🫶

🎀 SYNOPSIS 🎀

void __iomem * devm_pci_remap_cfgspace (struct device *dev ,
resource_size_t offset , resource_size_t size );

💖 ARGUMENTS 💖

• dev — the generic device to remap the IO address for. That's the whole vibe ✨
• offset — the resource address to map. Literally the "where" of it all 📍
• size — the size of the map. Gotta know how much space we're working with, no cap 📏

🌈 DESCRIPTION 🌈

Managed pci_remap_cfgspace. The map is automatically unmapped on driver detach — cleanup is handled, and that is lowkey iconic 🧚

🦋 SEE ALSO 🦋

• Kernel file ./drivers/pci/devres.c — the kernel file to peek at, bestie 👀
• devm_pci_remap_iospace(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)

Later, bestie 💜 This page came from ./drivers/pci, dated October 2026, and it's filed under devm_pci_remap_cfgspace(9). Slay and happy hacking ✨🎀