pinctrl_gpio...ection_input(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pinctrl_gpio_direction_input πŸ’…

okay so welcome to the Kernel API Manual, bestie ✨ the header/footer on this page spells it pinctrl_gpio...ection_input(9) β€” yes, with the little truncation moment β€” and the function we're actually here for is pinctrl_gpio_direction_input. it's giving β€œone tiny pin-control helper, very serious rules” energy, and we're gonna cover every detail fr fr.


🌸 NAME 🌸

pinctrl_gpio_direction_input β€” request a GPIO pin to go into input mode. like, you're asking the pin to listen instead of yell, and honestly? iconic.

πŸ¦‹ SYNOPSIS πŸ¦‹

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

πŸŽ€ ARGUMENTS πŸŽ€

  • gc β€” the GPIO chip structure from the GPIO subsystem. this is the controller-level struct, the main character of the GPIO situation.
  • offset β€” the hardware offset of the GPIO relative to the controller. it's the pin's exact spot inside that controller, lowkey important.

✨ DESCRIPTION ✨

So here's the vibe check: this function should ONLY be used from gpiolib-based GPIO drivers, as part of their gpio_direction_input semantics. that's the whole lane. platforms and individual drivers shall NOT touch pin control GPIO calls β€” not even a little, not even with a cute little side quest. it's a hard boundary, and we respect it periodt.

no cap: if you're not in a gpiolib-based GPIO driver doing its gpio_direction_input thing, this is not your function to call. the manpage is very clear, and the caps lock is doing a lot of emotional labor.

πŸ”₯ SEE ALSO πŸ”₯

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

all the see-also besties, in their exact little line-up 🫢:

okay that's the whole page, bestie 🫢 source path is ./drivers/pinctrl, the date is October 2026, and the page name in the footer is pinctrl_gpio...ection_input(9). mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from