driver_find_..._by_acpi_dev(9)

💖 NAME 💖

driver_find_device_by_acpi_dev — bestie, it's a device iterator, and its whole job is to go find you that one particular device that matches the ACPI_COMPANION device. Like a little scavenger hunt but for kernel devices 🎀

✨ SYNOPSIS ✨

struct device * driver_find_device_by_acpi_dev (const struct device_driver *drv , const struct acpi_device *adev );

So it hands you back a struct device * — the one you were looking for, iykyk 💅

🦋 ARGUMENTS 🦋

• drv — the driver we're iterating. Yes, "we." You and the kernel, doing this together, no cap. This is the driver whose devices get walked through, one by one 🔥
• adev — the ACPI_COMPANION device to match. This is the one we're matching against, literally the whole point of the search 🎯

🌈 SEE ALSO 🌈

Squad goals, all of them, in the order the page lists them:

• Kernel file ./include/linux/device/driver.h
• enum probe_type(9)
• struct device_driver(9)
• driver_find_device_by_name(9)
• driver_find_device_by_of_node(9)
• driver_find_device_by_fwnode(9)
• driver_find_device_by_devt(9)
• module_driver(9)
• builtin_driver(9)

Like, the whole friend group of finders. Go say hi to the rest of them 🫶

This page is from the Kernel API Manual — that's the header's manual name, folded in right here so nothing gets lost bestie 💖

Okay so that's the whole vibe! This gorgeous little number lives in ./include/linux/device, dated October 2026, and it's filed under driver_find_..._by_acpi_dev(9). Slay, iconic, periodt 🌸✨👑