acpi_dev_get_pci_dev(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… acpi_dev_get_pci_dev(9) β€” Kernel API Manual πŸŽ€

okay so bestie, welcome to the glow-up of the <pink>acpi_dev_get_pci_dev</pink> page from the Kernel API Manual ✨ this one's short and sweet, literally a little matchmaker function that hooks your ACPI device up with its PCI bestie πŸ’–


✨ NAME ✨

acpi_dev_get_pci_dev β€” get a struct pci_dev for a given ACPI device 🫢

🌸 SYNOPSIS 🌸

struct pci_dev * acpi_dev_get_pci_dev (struct acpi_device *adev );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • adev β€” your target ACPI device, the main character in question πŸ‘‘

πŸ’œ DESCRIPTION πŸ’œ

so what it does is: find the PCI device associated with adev, if any, and bump up its reference counter ✨ like it's giving matchmaker energy, it finds the PCI partner and then makes sure the refcount knows somebody's holding onto it now πŸ”₯

heads up bestie 😭 callers are responsible for dropping the PCI device reference obtained by this function. no cap, that's on you. don't just walk away from it πŸ’€

🌈 RETURN 🌈

the struct pci_dev pointer of a reference-counted PCI device on success 🌟 or NULL on failure πŸ™ˆ that's the whole vibe check.

πŸ“ SEE ALSO πŸ“


and that's the page, periodt πŸ’… this lil section lives in ./drivers/acpi, dated October 2026 πŸŽ€ and the page itself is literally called acpi_dev_get_pci_dev(9) β€” iykyk, slay, go drop that reference πŸ«ΆπŸ’–

πŸ“¦ where this page comes from