acpi_of_match_device(9)

✨ acpi_of_match_device ✨

okay so bestie, welcome to the kernel API manual for acpi_of_match_device — yes that's acpi_of_match_device(9), section 9, we're in the deep kernel lore today 💅

---

🎀 NAME 🎀

acpi_of_match_device — literally matches a device object using the "compatible" property 🦋

---

🌸 SYNOPSIS 🌸

bool acpi_of_match_device (const struct acpi_device *adev , const struct
of_device_id *of_match_table , const struct of_device_id **of_id );

---

💖 ARGUMENTS 💖

• adev — the ACPI device object you wanna match, bestie 🫶
• of_match_table — the list of device IDs we're matching against ✨
• of_id — the OF ID, but only if it actually matched 👑

---

🧚 DESCRIPTION 🧚

okay so here's the tea ☕ — if dev has an ACPI companion, and that companion has ACPI_DT_NAMESPACE_HID in its list of identifiers, and it's got a _DSD object with the "compatible" property? then we use that property to match against the given list of identifiers. that's the whole vibe check, no cap 💀

---

🔥 SEE ALSO 🔥

kernel file ./drivers/acpi/bus.c — go read it, iykyk 👀

• acpi_bus_notify(9)
• devm_acpi_install_notify_handler(9)
• acpi_bus_get_primary_device(9)
• acpi_get_first_physical_node(9)
• acpi_device_is_first_physical_node(9)
• acpi_set_modalias(9)
• acpi_match_acpi_device(9)
• acpi_match_device(9)
• acpi_bus_find_device_by_name(9)
• acpi_early_init(9)
• acpi_subsystem_init(9)

---

🍓 little sign-off from your girl: this page lives under ./drivers/acpi, dated October 2026, and it's giving iconic kernel documentation energy — periodt 💜🎀