PCI_DEVICE_DATA(9)

🌸 NAME — PCI_DEVICE_DATA(9) 🌸

okay so this is the PCI_DEVICE_DATA(9) page from the Kernel API Manual, and it’s literally about a macro used to describe a specific PCI device in very short form. Bestie, it’s tiny, it’s useful, it’s giving “one-line icon” energy 💅✨

---

✨ SYNOPSIS ✨

Here’s the whole vibe, no cap:

PCI_DEVICE_DATA (vend , dev , data );

---

🎀 ARGUMENTS 🎀

• vend — the vendor name, without the PCI_VENDOR_ID_ prefix 👑
• dev — the device name, without the PCI_DEVICE_ID_<vend>_ prefix 🦋
• data — the driver data to be filled 💖

---

🧚 DESCRIPTION 🧚

So what does this macro actually do? It creates a struct pci_device_id that matches a specific PCI device. The subvendor, and subdevice fields will be set to PCI_ANY_ID. That’s the whole assignment, and it ate. Periodt. 💅🔥

---

💜 SEE ALSO 💜

Kernel file: ./include/linux/pci.h

The whole crew, bestie:

• enum pci_interrupt_pin(9)
• pci_channel_state_t(9)
• pci_is_bridge(9)
• pci_is_vga(9)
• pci_is_display(9)
• struct pci_driver(9)
• PCI_DEVICE(9)
• PCI_DEVICE_DRIVER_OVERRIDE(9)
• PCI_DRIVER_OVERRIDE_DEVICE_VFIO(9)
• PCI_DEVICE_SUB(9)
• PCI_DEVICE_CLASS(9)
• PCI_VDEVICE(9)
• PCI_VDEVICE_SUB(9)
• pcie_capability_clear_and_set_word(9)
• pci_bus_for_each_resource(9)
• module_pci_driver(9)
• builtin_pci_driver(9)
• pci_irq_type(9)
• pci_irqd_intx_xlate(9)
• pci_resource_is_io(9)
• pci_resource_is_mem(9)
• pci_pcie_cap(9)
• pci_is_pcie(9)
• pcie_caps_reg(9)
• pci_pcie_type(9)
• pcie_find_root_port(9)
• pci_vpd_alloc(9)
• pci_vpd_find_id_string(9)
• pci_vpd_find_ro_info_keyword(9)
• pci_vpd_check_csum(9)
• pci_ari_enabled(9)
• pci_is_thunderbolt_attached(9)

---

okay that’s the page, bestie! Source/version: ./include/linux; date: October 2026; manual: PCI_DEVICE_DATA(9). Mwah 💋✨🫶