acpi_fetch_acpi_dev(9)

📦 version 7.3.1, in nixpkgs unstable

💅 acpi_fetch_acpi_dev

okay so first things first, this is a page from the Kernel API Manual (section 9, bestie, we're in kernel-internals territory 🧚) and it's all about one very specific little function. no cap, it's a short one, so let's get into it ✨

✨ NAME ✨

acpi_fetch_acpi_dev — Retrieve ACPI device object 💖

like, it goes and gets the device object for you. that's the whole vibe check.

🦋 SYNOPSIS 🦋

struct acpi_device * acpi_fetch_acpi_dev (acpi_handle handle );

so it hands you back a struct acpi_device * and it takes exactly one thing: an acpi_handle. iconic signature, no notes 🎀

🌸 ARGUMENTS 🌸

  • handle — the ACPI handle that's associated with the ACPI device object you're asking for 🫶 so like, this is your little claim ticket, and the function is the coat check.

👑 DESCRIPTION 👑

so here's what it does, and honestly it's giving "simple and reliable":

It returns a pointer to the ACPI device object associated with handle if present, or NULL otherwise. that's it. that's the function.

and like, the NULL case is not a bug, it's the function telling you "nope, nothing here bestie 💀" — so check your pointers before you dereference them, iykyk.

🔥 SEE ALSO 🔥

if you're going down this rabbit hole (and honestly, respect), the kernel file to peek at is:

./drivers/acpi/scan.c

and here are all the sibling functions in the same neighborhood, fr fr — go read them, they're literally all here:

tiny reminder: acpi_fetch_acpi_dev() gives you back NULL when there's no device for that handle — it does not invent one for you, so please don't treat it like it does 🙈

anyway that's the whole page!! short, sweet, very main character energy for such a small function ⭐

mwah 💋 go fetch those device objects responsibly

— this little gem lives in ./drivers/acpi, and the page is dated October 2026, filed under acpi_fetch_acpi_dev(9) 🍓 take care bestie, ily, bye!! 💜

📦 where this page comes from