gpio_device_find(9)

📦 version 7.3.1, in nixpkgs unstable

💅 gpio_device_find(9) — find a specific GPIO device 💅

hey bestie, welcome to the gpio_device_find(9) page from the Kernel API Manual ✨ this is the whole vibe for finding a specific GPIO device, and we're gonna get into it. 🎀

🌸 NAME 🌸

gpio_device_find — find a specific GPIO device

no cap, that's the whole name section: this helper is here to find a specific GPIO device. 💖

✨ SYNOPSIS ✨

okay so the signature is literally this, bestie — keep it exact:

struct gpio_device * gpio_device_find (const void *data , int
       (*match)(struct gpio_chip *gc, const void *data) );

🎀 ARGUMENTS 🎀

  • data — the data to pass to the match function. 🦋
  • match — callback function to check gpio_chip. 💅

💖 RETURN 💖

New reference to struct gpio_device. that's the return, bestie — a fresh reference, periodt. 🫶

🦋 DESCRIPTION 🦋

okay so this is similar to bus_find_device. it returns a reference to a gpio_device as determined by a user supplied match callback. ✨

the callback should return 0 if the device doesn't match and non-zero if it does. if the callback returns non-zero, this function will return to the caller and not iterate over any more gpio_devices. 🎯

the callback takes the GPIO chip structure as argument. during the execution of the callback function the chip is protected from being freed. 🛡️

🚨 TODO: This actually has yet to be implemented. bestie, that's the literal caveat — don't forget it. 💀

if the function returns non-NULL, the returned reference must be freed by the caller using gpio_device_put. please don't ghost your reference, that's not the move. 🙈

🌈 SEE ALSO 🌈

the kernel file is ./drivers/gpio/gpiolib.c, and here's the full cross-reference bestie list — every single one, no skips. 👑

and that's the page, bestie 🫶 — source: ./drivers/gpio · manual/version: Kernel API Manual · date: October 2026. periodt. 💅

📦 where this page comes from