pinctrl_gpi...ction_output(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pinctrl_gpi...ction_output(9) β€” from the Kernel API Manual

okay so bestie, welcome to the group chat πŸ’– this is the manual page for pinctrl_gpio_direction_output β€” yes the header is doing that truncated thing (pinctrl_gpi...ction_output(9), iconic of it) but the full name is right there in the NAME section, we got you 🫢


✨ NAME ✨

pinctrl_gpio_direction_output β€” politely ask a GPIO pin to go into output mode πŸŽ€


🌸 SYNOPSIS 🌸

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

like, that's the whole vibe. two args, one int back ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

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

πŸ’œ DESCRIPTION πŸ’œ

okay so here's the tea β˜• this function should *ONLY* be used from gpiolib-based GPIO drivers, as part of their gpio_direction_output semantics. that's the whole point of it, periodt πŸ’…

and because we love a clear boundary: platforms and individual drivers shall *NOT* touch pin control GPIO calls. nope. not them. not ever. this is a driver-only zone πŸ”₯

fr fr read that asterisk situation again β€” *ONLY* and *NOT* are not decorative, they're the whole rule 😭

⭐ SEE ALSO ⭐

the kernel file to go look at is ./drivers/pinctrl/core.c β€” and here's the full squad of friends, no cap, all of them:


and that's the page!! πŸ’–βœ¨πŸŽ€ source is ./drivers/pinctrl, dated October 2026 β€” ty for coming to my TED talk, go set some pins to output mode responsibly πŸ¦‹πŸ’…πŸ‘‘

πŸ“¦ where this page comes from