pinctrl_match_gpio_range(9)

📦 version 7.3.1, in nixpkgs unstable

💅 pinctrl_match_gpio_range(9) — from the Kernel API Manual, bestie ✨

okay so picture this: it's a Tuesday, you're deep in the kernel, and you need to know if some GPIO pin belongs to a pin controller's range. That's literally this function. Welcome to the group chat 🫶

🌸 NAME 🌸

pinctrl_match_gpio_range — the vibe check for "is this GPIO pin in range, or nah?" 💅

✨ SYNOPSIS ✨

struct pinctrl_gpio_range * pinctrl_match_gpio_range (struct pinctrl_dev
*pctldev , struct gpio_chip *gc , unsigned int offset );

yep, three args, one pointer back. no cap ✨

🎀 ARGUMENTS 🎀

  • pctldev — the pin controller device you wanna check. like, the one under investigation 🔍
  • gc — the GPIO chip structure, straight from the GPIO subsystem. it's the GPIO side of the story 🦋
  • offset — the hardware offset of the GPIO, relative to the controller. not absolute, okay? relative 🙈

💖 DESCRIPTION 💖

So what it does: it tries to match a GPIO pin number to the ranges handled by a certain pin controller. That's the whole mission 💫

If it matches, it returns the range. If it doesn't? NULL. That's it. Iconic, minimal, does one job and ate 👑

fr fr, that's the entire behaviour — no hidden side quests, no plot twists.

🌈 SEE ALSO 🌈

Kernel file: ./drivers/pinctrl/core.c

and the whole extended friend group that comes with it (yes, all of them, I'm not skipping a single one, that would be rude 💀):

that's the whole page, bestie 🍓 it lives in ./drivers/pinctrl, this version is dated October 2026, and the manual name is pinctrl_match_gpio_range(9) in case you forgot already 😭 go forth and match some ranges 💜🧚

📦 where this page comes from