__pci_device_probe(9)

💅 NAME 💅

__pci_device_probe — bestie, this is the little guy that checks if a driver actually wants to claim a specific PCI device 🎀

(also hi, this is the Kernel API Manual, section 9, welcome to the group chat ✨)

---

✨ SYNOPSIS ✨

int __pci_device_probe (struct pci_driver *drv , struct pci_dev *pci_dev );

Like, that's the whole signature. Short king. 👑

---

🫶 ARGUMENTS 🫶

• drv — the driver we're calling up to ask the big question: do you want this PCI device or not, bestie? 💖
• pci_dev — the PCI device currently getting probed, i.e. the main character of this exact moment 🌟

---

🔥 DESCRIPTION 🔥

okay so here's the tea: it returns 0 on success, else error. no cap, that's the whole return contract 😌

and the side-effect — the messy part, the iykyk — is that pci_dev->driver gets set to drv at the moment drv claims pci_dev. so like, the claiming is permanent-ish in the struct, it's giving "we're together now" energy 💀💍

ngl, remember that side-effect exists, because pci_dev->driver literally changes state out from under you. not a vibe to forget that 🫠

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/pci/pci-driver.c — go read it, it's the source of truth fr fr 📖

• do_pci_add_dynid(9)
• pci_add_dynid(9)
• do_pci_match_id(9)
• pci_match_id(9)
• pci_match_device(9)
• new_id_store(9)
• remove_id_store(9)
• pci_restore_standard_config(9)
• __pci_register_driver(9)
• pci_unregister_driver(9)
• pci_dev_driver(9)
• pci_bus_match(9)
• pci_dev_get(9)
• pci_dev_put(9)
• pci_uevent_ers(9)
• pci_dma_configure(9)

like, that's the whole friend group, go say hi to all of them 🦋💜

---

and that's the page, bestie!! this one lives under ./drivers/pci and is dated October 2026, so like, future-coded slay ⭐🌈 mwah, go probe something iconic 💅🎀