acpi_match_device(9)

📦 version 7.3.1, in nixpkgs unstable

💅 acpi_match_device — the acpi_match_device(9) page, but make it make sense

okay bestie, welcome to the kernel API manual, section 9, and today's main character is acpi_match_device. it's a kernel function, it lives in ./drivers/acpi, and it's about to match a struct device against a list of ACPI IDs. no cap. let's go 🎀

✨ NAME ✨

acpi_match_device — literally what it says on the tin: match a struct device against a given list of ACPI IDs 🦋

🌸 SYNOPSIS 🌸

const struct acpi_device_id * acpi_match_device (const struct acpi_device_id *ids , const struct device *dev );

like, that's the whole vibe right there 👑

🧚 ARGUMENTS 🧚

  • ids — the array of struct acpi_device_id objects you're matching against. this is your candidate list, your roster, your lineup 💖
  • dev — the device structure that's getting matched. the one being vibe-checked 🫶

🔥 DESCRIPTION 🔥

so here's the tea, bestie 🍓

it checks if dev has a valid ACPI handle, and then it checks if there's a struct acpi_device object for that handle — and then it uses that object to match against a given list of device IDs. yes, that's the whole arc. it's giving "look it up, then compare" energy and honestly? iconic 💅

and the return situation: it returns a pointer to the first matching ID on success, or NULL on failure. that's it. that's the deal. 😭

🌈 SEE ALSO 🌈

ok so that's the whole page!! every single thing is still here, i promise, i would never do you like that 🙈 the source is ./drivers/acpi, the date is October 2026, and this was brought to you by the Kernel API Manual, page acpi_match_device(9) — periodt. 💜✨

go read the whole SEE ALSO list, bestie, i believe in you 🧚‍♀️👑

📦 where this page comes from