On Wed, Oct 09, 2013 at 03:09:21PM +0200, Linus Walleij wrote: > It's more like the pin control core is passing the array of settings > to the driver and the behaviour is specified per-driver. > > So that is from the kernels point of view, no matter whether > device tree is used or not. A specific driver may instill specific > behaviour - sequential or not. Right, so that means doing this: pinctrl_usdhc1_1: usdhc1grp-1 { fsl,pins = < ... MX6QDL_PAD_SD1_DAT3__SD1_DATA3 0x17059 ... >; }; pinctrl_usdhc1_1_dat3cd: usdhc1grp-3 { fsl,pins = < MX6QDL_PAD_SD1_DAT3__SD1_DATA3 0x13059 >; }; and then: pinctrl-0 = <&pinctrl_usdhc1_1 &pinctrl_usdhc1_1_dat3cd>; can result in either "MX6QDL_PAD_SD1_DAT3__SD1_DATA3 0x17059" or "MX6QDL_PAD_SD1_DAT3__SD1_DATA3 0x13059" being the final configuration for that pin. What that means is that for any pinctrl setting, pins to be configured must be mentioned exactly once and once only. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html