STRUCT GEMINI_PIN_GROUP(9)

🌸 NAME 🌸

struct gemini_pin_group — describes a Gemini pin group. that's the whole vibe, bestie: it's the struct that describes a Gemini pin group, and it's lowkey the blueprint for the pin-group situation. 💖

okay so welcome to struct gemini_pin_group(9) from the Kernel API Manual — we're about to get into the pin-group lore, and it's giving very structured, very pinctrl. ✨

✨ SYNOPSIS ✨

no cap, the struct literally looks like this:

struct gemini_pin_group {
    const char *name;
    const unsigned int *pins;
    const unsigned int num_pins;
    u32 mask;
    u32 value;
    u32 driving_mask;
};

🎀 Members 🎀

• name — the name of this specific pin group. it's the iconic identifier behavior, fr fr. 💅
• pins — an array of discrete physical pins used in this group, taken from the driver-local pin enumeration space. yep, that's the pin neighborhood. 🦋
• num_pins — the number of pins in this group array, i.e. the number of elements in .pins so we can iterate over that array. it's the count bestie, so the loop can slay. 🔥
• mask — bits to clear to enable this when doing pin muxing. clear these bits, periodt. ✨
• value — bits to set to enable this when doing pin muxing. set these bits, no cap. 💖
• driving_mask — bitmask for the IO Pad driving register for this group, if it supports altering the driving strength of its lines. only when that support is there, iykyk. 🫶

🌈 SEE ALSO 🌈

• Kernel file ./drivers/pinctrl/pinctrl-gemini.c — and the structs struct gemini_pin_conf(9), struct gemini_pmx(9), and struct gemini_pmx_func(9) are right there for you to check. go read them, bestie. 💜

xoxo, your pinctrl bestie 💅 — source/version: ./drivers/pinctrl; date: October 2026. 🫶