for_each_req...pio_in_range(9)

💅 for_each_requested_gpio_in_range — Kernel API Manual (yes that's the manual name, we're fancy)

okay so bestie, picture this: you've got a range of GPIOs and you only care about the ones that somebody actually requested. This thing iterates over requested GPIOs in a given range 🎀 That's it. That's the whole vibe. No cap.

It's literally the iterator your for-loop dreams are made of ✨

---

✨ SYNOPSIS ✨

for_each_requested_gpio_in_range (_chip , _i , _base , _size , _label );

(the spaces are exactly like that, don't @ me, copy it verbatim or it won't compile 🔥)

---

🌸 ARGUMENTS 🌸

• _chip — the chip to query 🫶 like, which chip are we even talking to here
• _i — the loop variable 💫 your classic i, doing main character energy work
• _base — first GPIO in the range ⭐ where the party starts
• _size — amount of GPIOs to check starting from _base 🎀 so it's _base onward, _size of them, got it
• _label — label of current GPIO 🦋 the little name tag so you know which one you're looking at

---

every single one of those args gets passed in exactly as written, underscore and all — they're the macro's own names, not placeholders for you to rename 💀

---

👑 SEE ALSO 👑

like, go read these next, they're iconic:

• Kernel file ./include/linux/gpio/driver.h
• struct gpio_irq_chip(9)
• struct gpio_chip(9)
• for_each_hwgpio_in_range(9)
• for_each_hwgpio(9)
• gpiochip_add_data(9)
• struct gpio_pin_range(9)

---

and that's the whole page, bestie 🌈 mwah 💋

This absolute gem comes to you from ./include/linux/gpio, dated October 2026 — periodt, that's the sign-off, go touch some hardware 🧚‍♀️💜