pcie_pme_handle_request(9)

💅 pcie_pme_handle_request(9) — Kernel API Manual

okay bestie so this is a page from the Kernel API Manual, and the star of the show is pcie_pme_handle_request ✨ — literally the function that goes "hmm, who woke me up?" and then deals with them 🫶

🌸 NAME 🌸

pcie_pme_handle_request — find the device that generated the PME and, like, handle it 💅 periodt.

✨ SYNOPSIS ✨

void pcie_pme_handle_request (struct pci_dev *port , u16 req_id );

no cap, that's the whole signature. two arguments, zero drama, returns void because it doesn't owe you an answer 😌

🎀 ARGUMENTS 🎀

• port — the Root port or the event collector that generated the PME interrupt 👑 this is the one holding the aux cord, basically.
• req_id — the PCIe Requester ID of the device that generated the PME 🦋 iykyk, it's the "who did this" tag.

🔥 SEE ALSO 🔥

Kernel file ./drivers/pci/pcie/pme.c — that's where the lore lives 📖 and while you're there, go say hi to the whole friend group:

• pcie_pme_interrupt_enable(9)
• pcie_pme_walk_bus(9)
• pcie_pme_from_pci_bridge(9)
• pcie_pme_work_fn(9)
• pcie_pme_irq(9)
• pcie_pme_can_wakeup(9)
• pcie_pme_mark_devices(9)
• pcie_pme_probe(9)
• pcie_pme_suspend(9)
• pcie_pme_resume(9)
• pcie_pme_remove(9)
• pcie_pme_init(9)

they're all in their main character era over in ./drivers/pci/pcie 🧚💜

and that's the whole page, bestie 💖 shoutout to the source ./drivers/pci/pcie and the October 2026 date stamp — iconic of them, honestly 🎀 slay, go handle some PMEs 👑🌺