pinctrl_gpio_request(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pinctrl_gpio_request β€” the Kernel API Manual, bestie edition ✨

okay so you're in the Kernel API Manual and the page you opened is pinctrl_gpio_request(9). buckle up, this one's short but the DRAMA is real πŸŽ€


✨ NAME ✨

pinctrl_gpio_request β€” request a single pin to be used as GPIO πŸ¦‹


🌸 SYNOPSIS 🌸

int pinctrl_gpio_request (struct gpio_chip *gc , unsigned int offset );

πŸ’– ARGUMENTS πŸ’–

  • gc β€” the GPIO chip structure, straight from the GPIO subsystem πŸ‘‘
  • offset β€” the hardware offset of the GPIO relative to the controller, iykyk πŸ“

πŸ”₯ DESCRIPTION πŸ”₯

This function should *ONLY* be used from gpiolib-based GPIO drivers, as part of their gpio_request semantics. like, literally only those, no cap πŸ™ˆ

platforms and individual drivers shall *NOT* request GPIO pins to be muxed in. not your job, bestie, stay in your lane πŸ’…

🌈 SEE ALSO 🌈

Kernel file ./drivers/pinctrl/core.c β€” plus the whole friend group, fr fr:


and that's the whole vibe check, bestie 🫢 this page came from ./drivers/pinctrl, dated October 2026 β€” go forth and request responsibly, mwah πŸ’œπŸ§šβ­

πŸ“¦ where this page comes from