pin_request(9)

💅 pin_request(9) — like, the whole vibe

okay so bestie, welcome to pin_request(9), straight out of the Kernel API Manual ✨ this is the little kernel function that politely asks for one single pin to get muxed in — and yeah, it's typically for GPIO 🎀

🌸 NAME

pin_request — request a single pin to be muxed in, typically for GPIO 🫶

✨ SYNOPSIS

int pin_request (struct pinctrl_dev *pctldev , int pin , const char
*owner , struct pinctrl_gpio_range *gpio_range );

like, that's the whole signature, no notes 💅

🦋 ARGUMENTS

• pctldev — the pin controller device this whole thing is associated with, iykyk 🔥
• pin — the pin number, but specifically in the global pin space, don't get it twisted
• owner — a representation of who owns this pin 👑 typically it's the device name that controls its mux function, or the requested GPIO name — so like, it's the pin's ~parent~ fr fr
• gpio_range — the range matching the GPIO pin, but only if this is a request for a single GPIO pin 🎀

🌈 SEE ALSO

Kernel file ./drivers/pinctrl/pinmux.c — and like, the whole friend group 💖:

• pinmux_can_be_used_for_gpio(9)
• pin_free(9)
• pinmux_request_gpio(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)

mwah 💋 that's the page — brought to you by ./drivers/pinctrl, dated October 2026, and yes the header said pin_request(9) the whole time, slay ⭐