pci_pme_wakeup(9)

📦 version 7.3.1, in nixpkgs unstable

💖 pci_pme_wakeup(9) — the "wake up bestie, your PME status is giving" page 💖

okay so this is straight out of the Kernel API Manual, and it's honestly such a small mood but it does so much. let's get into it 🫶

✨ NAME ✨

pci_pme_wakeup — wake up a PCI device if its PME Status bit is set. that's it, that's the whole vibe. if the bit's up, we're up 💅

🌸 SYNOPSIS 🌸

int pci_pme_wakeup (struct pci_dev *dev , void *pme_poll_reset );

yes it returns an int, yes it takes a struct pci_dev * and a void *, and yes the void * is named pme_poll_reset and it's lowkey doing emotional labor. look at her go ✨

🎀 ARGUMENTS 🎀

  • dev — the device to handle. this is the main character of the whole operation, no cap 🔥
  • pme_poll_reset — whether or not to reset the device's pme_poll flag. that's the whole job description bestie, it's a yes/no kinda situation 🙈

🦋 DESCRIPTION 🦋

so here's the tea: we check if dev has generated PME — and if she has, we queue a resume request for it. that's the whole flow. she brought the PME, we bring the resume request. iconic behavior honestly 👑

like it's literally just: check the vibe (did this device generate PME?), and if yes, queue a resume request. simple. clean. slay 💅

⭐ SEE ALSO ⭐

first up, the actual kernel file where this lives — ./drivers/pci/pci.c. go read the source bestie, it's giving transparency 💖

and then... the extended family. the whole friend group. the entire group chat. ngl there are so many of these and honestly? every single one of them is here, i did not skip a single one, i would never do that to you 🫶

like i said. the whole group chat. every single one invited to the party 🎉

ok and that's the page bestie 💜 wake the device, check the PME status bit, queue the resume request, log off. iykyk.

that's a wrap on pci_pme_wakeup(9), filed under ./drivers/pci in the Kernel API Manual, dated October 2026 — mwah, go touch some PCI config space, ily 🎀💖✨

📦 where this page comes from