STRUCT WINBOND_GPIO_INFO(9)

💖 struct winbond_gpio_info(9) 💖

okay so bestie, welcome to the Kernel API Manual ✨ — this one's all about struct winbond_gpio_info, which is literally the whole info packet for one particular GPIO port (a device). yes. one struct, one port, one vibe. 🌸

---

🎀 NAME 🎀

struct winbond_gpio_info — all the deets about a particular GPIO port (device). it's giving "knows everything about its one port" energy and honestly? iconic. 👑

---

✨ SYNOPSIS ✨

struct winbond_gpio_info {
    u8 dev;
    u8 enablereg;
    u8 enablebit;
    u8 outputreg;
    u8 outputppbit;
    u8 ioreg;
    u8 invreg;
    u8 datareg;
    struct winbond_gpio_port_conflict conflict;
 };

like, look at it. so many u8s. so organized. we love a structured queen. 💅

---

🦋 Members 🦋

• dev — the Super I/O logical device number for all the registers listed down below. like the address of the whole squad 💜
• enablereg — the register number that holds the port enable bit
• enablebit — and this is which bit in there actually turns the port on, index-style ✨
• outputreg — register number for the output driver mode bit
• outputppbit — index of the push-pull output driver mode bit, slay 🫶
• ioreg — the data direction register number (in or out, bestie, gotta know)
• invreg — the pin data inversion register number
• datareg — the pin data register number, i.e. the actual data lives here 🔥
• conflict — a description of a device that possibly conflicts with this port. so like, the messy ex of this port 💀 pay attention to this one fr fr

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/gpio/gpio-winbond.c
• struct winbond_gpio_port_conflict(9)

---

lowkey a reminder bestie: conflict is only a possible conflict, not a guaranteed beef. no cap, read the other struct before you panic 🙈

---

okay that's the whole page, mwah 💋 — this was the Kernel API Manual, from ./drivers/gpio, dated October 2026, and it was a whole moment. go forth and GPIO responsibly, bestie 🧚⭐🍓