pinmux_request_gpio(9)

💅 pinmux_request_gpio — it's giving "bestie, request that GPIO pinmuxing" ✨

okay so this is from the Kernel API Manual, and it's the glow-up page for pinmux_request_gpio(9) — the little function that asks for pinmuxing on a GPIO pin. no cap, it's a short one, but every detail is here and accounted for 🫶

---

🌸 NAME 🌸

pinmux_request_gpio — request pinmuxing for a GPIO pin 💖

---

✨ SYNOPSIS ✨

int pinmux_request_gpio (struct pinctrl_dev *pctldev , struct
       pinctrl_gpio_range *range , unsigned int pin , unsigned int gpio );

like, that's the whole signature. iconic. no notes. 👑

---

🎀 ARGUMENTS 🎀

• pctldev — the pin controller device that's affected, aka the main character here 💅
• range — the applicable GPIO range, the vibes-appropriate zone for this pin 🦋
• pin — the pin to mux in for GPIO, literally the pin we're setting up 🌸
• gpio — number of requested GPIO, the actual GPIO number being asked for 🔥

---

👀 SEE ALSO 👀

the kernel file is ./drivers/pinctrl/pinmux.c, and it's linked up with all of these besties:

• pinmux_can_be_used_for_gpio(9)
• pin_request(9)
• pin_free(9)
• pinmux_free_gpio(9)
• pinmux_gpio_direction(9)
• pinmux_generic_get_function_count(9)
• pinmux_generic_get_function_name(9)
• pinmux_generic_get_function_groups(9)
• pinmux_generic_get_function(9)
• pinmux_generic_function_is_gpio(9)
• pinmux_generic_add_function(9)
• pinmux_generic_add_pinfunction(9)
• pinmux_generic_remove_function(9)
• pinmux_generic_free_functions(9)

---

bestie, that's the whole page — short, sweet, and very pinmux-coded 🧚💜

---

and yes, the sign-off details are giving source/version/date realness: it's from ./drivers/pinctrl, dated October 2026, and the page is pinmux_request_gpio(9). periodt 💫