STRUCT MVEBU_MPP_CTRL(9)

💖 NAME 💖

struct mvebu_mpp_ctrl — describe a mpp control. okay so this is the struct mvebu_mpp_ctrl(9) page from the Kernel API Manual, bestie 💅✨.

✨ SYNOPSIS ✨

here’s the exact struct shape, no edits, no vibes-based rewrites 🫶:

struct mvebu_mpp_ctrl {
    const char *name;
    u8 pid;
    u8 npins;
    unsigned *pins;
    int (*mpp_get)(struct mvebu_mpp_ctrl_data *data, unsigned pid,
unsigned long *config);
    int (*mpp_set)(struct mvebu_mpp_ctrl_data *data, unsigned pid,
unsigned long config);
    int (*mpp_gpio_req)(struct mvebu_mpp_ctrl_data *data, unsigned pid);
    int (*mpp_gpio_dir)(struct mvebu_mpp_ctrl_data *data, unsigned pid,
bool input);
 };

🫶 Members 🫶

• name — name of the control group 🎀
• pid — first pin id handled by this control 📍
• npins — number of pins controlled by this control 🔢
• mpp_get — (optional) special function to get mpp setting 🫶
• mpp_set — (optional) special function to set mpp setting ✨
• mpp_gpio_req — (optional) special function to request gpio 🦋
• mpp_gpio_dir — (optional) special function to set gpio direction 🎀

🌸 Description 🌸

okay so picture a muxable unit inside the SoC — could be a pin, a group of pins, or an internal function. that’s what a mpp_ctrl describes, periodt 💅. Each muxable unit can be switched between two or more different settings, like assigning mpp pin 13 to uart1 or sata 👑.

The mpp_get/_set functions are mandatory — no cap, they’re the ones used to get/set a specific mode 🔥. The optional mpp_gpio_req/_dir functions can be used to allow pin settings with varying gpio pins 🦋. slay ✨.

🔥 SEE ALSO 🔥

Kernel file ./drivers/pinctrl/mvebu/pinctrl-mvebu.h struct mvebu_mpp_ctrl_data(9), struct mvebu_mpp_ctrl_setting(9), struct mvebu_mpp_mode(9), struct mvebu_pinctrl_soc_info(9) 🫶

and that’s the whole page, bestie! 💖 source/version: ./drivers/pinctrl/mvebu · date: October 2026 · manual page: struct mvebu_mpp_ctrl(9). mwah 💅✨