[PATCH v2 3/4] scmi: pinctrl: add pinctrl driver for SCMI
Dan Carpenter
dan.carpenter at linaro.org
Tue Mar 24 16:07:13 CET 2026
On Tue, Mar 24, 2026 at 02:19:34PM +0100, Linus Walleij wrote:
> On Wed, Mar 11, 2026 at 8:41 PM Dan Carpenter <dan.carpenter at linaro.org> wrote:
>
> > scmi_pinctrl: protocol at 19 {
> > reg = <0x19>;
> > pinmux1: pinmux_test {
> > pinmux = <0 1 0xFFFFFFFF 18 1
> > 0 2 0xFFFFFFFF 18 1
> > 0 3 0xFFFFFFFF 18 1>;
> > function = "f_gpio1";
> > groups = "grp_1", "grp_3";
> > };
> > };
> >
> > Under linux the pinctrl subsystem will parse the function and group
> > properties and use that to handle muxing. However, under u-boot the
> > pin muxing is done using the "pinmux" property, which feeds raw SCMI
> > pinctrl PINCTRL_SETTINGS_CONFIGURE commands to the server. The
> > numbers are: selector, identifier, function_id, config_type, and
> > config_value. In the example above, it sets pins 1, 2, and 3 to 1.
> > The linux-kernel ignores this pinmux property.
>
> This whole thing is a bit of a hack and shortcut to make hard things
> simple isn't it?
I'm not disagreeing with you at all, but handling the default pinmux
property is the only mandatory part of a pin controller driver in
u-boot.
regards,
dan carpenter
More information about the U-Boot
mailing list