do_pci_add_dynid(9)

📦 version 7.3.1, in nixpkgs unstable

💅 do_pci_add_dynid(9) — the Kernel API Manual glow-up ✨

Okay bestie, so this is a page from the Kernel API Manual and it's literally about do_pci_add_dynid — adding a new PCI device ID to a driver and then making it re-probe. No cap, it's giving "tiny function, big consequences" energy. Let's get into it 🫶

✨ SYNOPSIS ✨

int do_pci_add_dynid (struct pci_driver *drv , const struct
       pci_device_id *id , bool check_dup );

That's the whole vibe right there — it takes your driver, your shiny new ID, and a lil' boolean that decides whether it should check for duplicates first. Periodt. 💅

🎀 ARGUMENTS 🎀

  • drv — your target PCI driver 👑 this is the main character that's gonna get the new ID
  • id — the ID to be added 🦋 like, the new friend joining the group chat
  • check_dup — a bool that says whether to check if a matching ID is already present 💀 because we do NOT want duplicates in this house

🌸 DESCRIPTION 🌸

So here's the tea, bestie: this function adds a new dynamic PCI device ID to your driver, and then it causes the driver to probe for all devices again. Like, it literally goes "hey everybody, re-check everything, we've got a new ID in town" 🔥

⚠️ Important: drv must have been registered prior to calling this function. Don't skip that step, I'm begging you 😭 register first, call after. That's the order. That's the assignment.

💀 CONTEXT 💀

It does GFP_KERNEL allocation. So heads up, this is doing memory stuff in a way that can sleep — keep that in mind, iykyk 🧚

💖 RETURN 💖

  • 0 on success — slay, it worked ✨
  • -errno on failure — not slay, but at least you get an error code to work with 🙈

🌈 SEE ALSO 🌈

The whole squad, fr fr — all of these are in the Kernel file ./drivers/pci/pci-driver.c:

Like, go read them if you want the full lore 📚💜

💌 Sign-off time, besties: this cute lil' page lives in ./drivers/pci and it's dated October 2026. Bye, love you, go register your driver first! 🎀🫶💅
📦 where this page comes from