STRUCT PINCTRL_MAP(9)

✨ NAME ✨

okay bestie, welcome to the tea on struct pinctrl_map(9) — yes, from the Kernel API Manual — and the short version is literally: boards/machines shall provide this map for devices. periodt 💅

🦋 SYNOPSIS 🦋

here's the shape of her, exactly:

       struct pinctrl_map {
           const char *dev_name;
           const char *name;
           enum pinctrl_map_type type;
           const char *ctrl_dev_name;
           union {
             struct pinctrl_map_mux mux;
             struct pinctrl_map_configs configs;
           } data;
        };

🎀 Members 🎀

• dev_name — the name of the device using this specific mapping. The name must be the same as in your struct device*. and heads up 👀 if this name is set to the same name as the pin controller's own dev_name, the map entry will be hogged by the driver itself upon registration.
• name — the name of this specific map entry for the particular machine. This is the parameter passed to pinmux_lookup_state ✨
• type — the type of mapping table entry.
• ctrl_dev_name — the name of the device controlling this specific mapping; the name must be the same as in your struct device*. This field is not used for PIN_MAP_TYPE_DUMMY_STATE 🫶
• data — Data specific to the mapping type.

🔥 SEE ALSO 🔥

Kernel file ./include/linux/pinctrl/machine.h, struct pinctrl_map_mux(9), struct pinctrl_map_configs(9) — go read those too bestie, iykyk 🌸

mwah 💖 source/version: ./include/linux/pinctrl, date: October 2026, title: struct pinctrl_map(9). byeee ✨🦋