of_gpio_twocell_xlate(9)

💫 of_gpio_twocell_xlate — the kernel API manual, but make it make sense 💫

okay so bestie, welcome to the manual page for of_gpio_twocell_xlate(9) — this is a Kernel API Manual situation, and honestly? it's a short one. we love a low-commitment read. 🎀

---

🌸 NAME 🌸

of_gpio_twocell_xlate — translate twocell gpiospec to the GPIO number and flags

like, it takes your twocell gpiospec and hands you back the GPIO number and the flags. both. at once. multitasking icon behavior. ✨

---

🦋 SYNOPSIS 🦋

int of_gpio_twocell_xlate (struct gpio_chip *gc , const struct
       of_phandle_args *gpiospec , u32 *flags );

🎀 ARGUMENTS 🎀

• gc — pointer to the gpio_chip structure. it's giving "here's my chip, pls look at it". 👑
• gpiospec — the GPIO specifier as found in the device tree. straight out of the device tree, no cap. 🌳
• flags — a flags pointer to fill in. you hand it an empty cup and this function pours flags into it. 🍓

---

💅 DESCRIPTION 💅

so like — this is a simple translation function, and i mean that lovingly. it's suitable for the most 1:1 mapped GPIO chips, aka the ones where the mapping is just... the mapping. no glow-up required. 🦋

and check this: this function performs only one sanity check — whether the GPIO is less than ngpios (which is specified in the gpio_chip). that's it. that's the whole vibe check. one check. not me being like "is that enough??" and the answer is: for 1:1 mapped chips? yeah bestie, it ate. 🔥

lowkey important: only that one check happens here. if you were expecting more validation, this is not that function. 🙈

---

⭐ RETURN ⭐

• GPIO number (>= 0) on success 🎉
• negative errno on failure 😭

like, if the number is zero or above, she slayed. if it's negative, that's an errno and something went sideways. periodt. 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpio/gpiolib-of.c — yes, the whole file, it's in the see-also and it's iconic for it 💜
• of_gpio_named_count(9)
• of_gpio_spi_cs_get_count(9)
• of_get_named_gpiod_flags(9)
• of_gpiochip_remove_hog(9)
• of_gpio_threecell_xlate(9) — yes, the threecell one. two's company, three's a trilogy. 🧚

---

okay that's the page!! 🫶 and for the cute sign-off: this one lives over in ./drivers/gpio, dated October 2026, and it's the of_gpio_twocell_xlate(9) page from the Kernel API Manual. go read the threecell one next, iykyk. 💖🌸✨