acpi_get_gpiod_from_data(9)

📦 version 7.3.1, in nixpkgs unstable

💅 acpi_get_gpiod_from_data — like, the kernel API manual page, bestie

okay so real talk, this is from the Kernel API Manual and it's about acpi_get_gpiod_from_data, which is literally the function that gets you a GPIO descriptor from an ACPI data node. yes bestie, that's the whole vibe. let's go 🎀

✨ SYNOPSIS ✨

int acpi_get_gpiod_from_data (struct fwnode_handle *fwnode , const char
*propname , struct acpi_gpio_lookup *lookup );

look at her. three params. returns an int. iconic behavior honestly 🫶

🌸 ARGUMENTS 🌸

  • fwnode — pointer to an ACPI firmware node 💖 this is where the GPIO info is gonna come from, so like, point it at the right one please
  • propname — the property name of the GPIO, yep that's it, that's the whole thing
  • lookup — pointer to a struct acpi_gpio_lookup that gets filled in 🦋 she's empty on the way in and full of answers on the way out

💫 DESCRIPTION 💫

so the way this works is, the function uses the property-based GPIO lookup to get to the GPIO resource — with all the relevant info — from a data-only ACPI firmware node, and then it uses that to obtain the GPIO descriptor and hand it back to you. periodt. ✨

the lookup gets filled with the GPIO descriptor you're supposed to use with the Linux generic GPIO API. very much "here's your descriptor bestie, go off" energy 💅

and if the GPIO cannot be translated? 😭 yeah that's an error return. no descriptor for you. it happens, don't take it personally.

🔥 RETURN 🔥

  • 0 on success — slay 💖
  • negative errno on failure — the sad path 🙈

🎀 SEE ALSO 🎀

kernel file ./drivers/gpio/gpiolib-acpi-core.c, plus all these absolute legends:

iykyk, that's a whole friend group of functions and you should absolutely go read them 🧚

aaaaand that's the page!! 🍓 coming at you from ./drivers/gpio, dated October 2026, and the title is of course acpi_get_gpiod_from_data(9) — mwah, go forth and get those descriptors 💜⭐

📦 where this page comes from