for_each_hwgpio_in_range(9)

💅 for_each_hwgpio_in_range(9) — from the Kernel API Manual, bestie ✨

Okay so picture this: it's you, a gpio_chip, and a whole range of GPIOs that need iterating. This macro is your girl. It iterates over all GPIOs in a given range, no cap, and honestly? Iconic behaviour. 🎀

🌸 SYNOPSIS 🌸

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

That's literally the whole invocation. Five args. Eat it up. 🍓

✨ ARGUMENTS ✨

• _chip — the chip you're iterating over. The motherboard main character energy. 👑
• _i — the loop counter. She's counting, she's keeping track, she's doing the work behind the scenes. 💅
• _base — the first GPIO in the ranger. (And yes, the manpage really says "ranger" — not range — that's canon now, we're keeping it, love her for it 🫶)
• _size — how many GPIOs to check, starting from _base. Like, the size of the squad. 🌈
• _label — the place where you store the address of the label if the GPIO is requested. Aka: if somebody's using it, you get the name. And for unused GPIOs? Set it to NULL. Empty slot, no drama, moving on. ⭐

💀 Real talk: _label only gets a label when the GPIO is requested — for unused ones it's NULL. Don't go reading it expecting a name that isn't there.

👀 SEE ALSO 👀

All the besties in the same friend group:

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

💖 that's the page, bestie — go iterate slayfully 💖

Dropping this from ./include/linux/gpio, dated October 2026, and it's signed the for_each_hwgpio_in_range(9) way. 🦋 Not me getting emotional over a kernel macro. 😭