pci_msi_regi...ode_provider(9)

💖 NAME 💖

okay so bestie, welcome to the pci_msi_regi...ode_provider(9) page from the Kernel API Manual — the function is literally called pci_msi_register_fwnode_provider, and it is the “Register callback to retrieve fwnode” one. 💅✨

🎀 SYNOPSIS 🎀

void pci_msi_register_fwnode_provider (struct fwnode_handle
*(*fn)(struct device *) );

🦋 ARGUMENTS 🦋

• fn — the callback matching a device to a fwnode that identifies a PCI MSI domain. It’s giving very specific matchmaker energy, no cap. 💖

🌸 DESCRIPTION 🌸

This should be called by the irqchip driver — the one that is the parent of the MSI domain — so it can provide a callback interface to query the fwnode. That’s the whole assignment. 🫶

🌈 SEE ALSO 🌈

Kernel file: ./drivers/pci/pci-acpi.c

And the whole SEE ALSO squad is:

• pciehp_is_native(9)
• shpchp_is_native(9)
• pci_acpi_wake_bus(9)
• pci_acpi_wake_dev(9)
• pci_acpi_add_root_pm_notifier(9)
• pci_acpi_add_pm_notifier(9)
• pci_dev_acpi_reset(9)
• pci_acpi_set_companion_lookup_hook(9)
• pci_acpi_clear_companion_lookup_hook(9)
• pci_acpi_optimize_delay(9)
• pci_host_bridge_acpi_msi_domain(9)

okay bye bestie 🫶 — the footer’s source/version bit is ./drivers/pci, the date is October 2026, and the footer title is pci_msi_regi...ode_provider(9). periodt 💅✨