STRUCT ABX500_GPIO_IRQ_CLUSTER(9)

🌸 struct abx500_gpio_irq_cluster(9) 🌸

okay bestie so this is a page from the Kernel API Manual — yeah the running header gets all chopped up and reads like struct abx50..._irq_cluster(9) because apparently nobody could afford the extra characters 😭 but it's the same thing, i promise.

✨ NAME ✨

struct abx500_gpio_irq_cluster — the lil struct that tells you which GPIOs are interrupt capable 💅

🎀 SYNOPSIS 🎀

struct abx500_gpio_irq_cluster {
    int start;
    int end;
    int to_irq;
 };

that's the whole vibe. three ints, zero drama. 🦋

💖 Members 💖

• start — the pin number of the first pin that's interrupt capable. like, the beginning of the squad 🫶
• end — the pin number of the last pin that's interrupt capable. the end of the squad. the squad boundaries are real 🔥
• to_irq — okay so here's the situation: the ABx500 GPIO's associated IRQs are clustered together throughout the interrupt numbers at irregular intervals. which, yeah, is a whole mess 😭 so to solve this quandary, the read-in values get placed into the cluster information table. that's the fix. that's the coping mechanism. iconic honestly 👑

🌈 SEE ALSO 🌈

• Kernel file ./drivers/pinctrl/nomadik/pinctrl-abx500.h
• struct abx500_function(9)
• struct abx500_pingroup(9)
• struct alternate_functions(9)
• struct abx500_pinrange(9)
• struct abx500_pinctrl_soc_data(9)

go read those next, they're all in the same friend group fr fr 💜

ngl this one's short and sweet — but the details still matter, so here's your sign-off 💌: this page lives under ./drivers/pinctrl/nomadik, and it's dated October 2026. slay, go forth and cluster those IRQs ✨🎀