STRUCT WINBOND_GPIO_PORT_CONFLICT(9)

💅 NAME 💅

struct winbond_gpio_port_conflict — literally the info about a device that might be beefing with you

okay bestie, so this struct is like the little warning label on a GPIO port, right? it's holding the deets on a possibly-conflicting device so the kernel can do a vibe check before anything messy happens 🫶

✨ SYNOPSIS ✨

struct winbond_gpio_port_conflict {
    const char *name;
    u8 dev;
    u8 testreg;
    u8 testbit;
    bool warnonly;
 };

look at her. five fields. main character energy 👑

🎀 Members 🎀

• name — the device name, periodt. and if it's NULL? that means no conflicting device is defined at all, so like… nothing to worry about here, bestie 💖
• dev — the Super I/O logical device number where the testreg register lives. or you can pass WB_SIO_DEV_NONE, which is the "don't select any logical device" option — iconic lowkey opt-out 🌸
• testreg — the register number where the testbit bit is chillin'. that's where we go lookin' 🔍
• testbit — the index of the bit we check to see whether an actual conflict exists. like, is there really drama or are we imagining it 😭
• warnonly — if this is set, then a conflict isn't fatal (we just warn about it, no biggie, we're being chill 💅). otherwise — and this is the important part — the particular GPIO port gets disabled if a conflict is detected. so if you leave it unset, the port is gone. not me forgetting to set that flag 🙈

👑 SEE ALSO 👑

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

fr fr go read struct winbond_gpio_info(9) next, it's the companion piece, iykyk 🦋

that's the whole page bestie, go slay some GPIO ports 🌈✨

signed off from ./drivers/gpio — October 2026 — mwah, drink water, and may your conflicts always be warnonly 🍓💜