* Adam Ford <aford173@xxxxxxxxx> [170619 16:21]: > Maybe, I missed something, so I apologize in advance, if this was > already discussed. I've been away for a bit. > > I have an OMAP3630 board running 4.11.y, and it's throwing some notes: > > [ 0.915374] pinctrl-single 48002030.pinmux: please update dts to > use #pinctrl-cells = <1> > [ 0.917297] pinctrl-single 48002030.pinmux: 284 pins at pa fa002030 size 568 > [ 0.917816] pinctrl-single 48002a00.pinmux: please update dts to > use #pinctrl-cells = <1> > [ 0.918243] pinctrl-single 48002a00.pinmux: 46 pins at pa fa002a00 size 92 > [ 0.919128] pinctrl-single 480025a0.pinmux: please update dts to > use #pinctrl-cells = <1> > [ 0.919525] pinctrl-single 480025a0.pinmux: 46 pins at pa fa0025a0 size 92 > > > What's interesting is that both the OMAP3 and OMAP3630 show the > #pinctrl-cells = <1> in the areas where I would expect. Any ideas why > the pinctrl would thow this message to update the dts file when they > appear to already be there? This happens with new kernel and old dtb file, right? We have pinctrl-single.c now using generic pinctrl parsing which has #pinctrl-cells in the binding. If #pinctrl-pins is not defined we currently default to 1 with a quirk. Best to update the dts if possible like the warning says. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
