Hi, * Adam Ford <aford173@xxxxxxxxx> [190406 11:30]: > Is this something you want done for the omap3 as well? If this get's > pulled in for am33xx, I can work on doing it for omap3 unless someone > else already is. Sure.. There are few things to consider for omap3 though. The padconf modes are different between various SoC revisions. I think the base register range should be the same though. This can be checked in git history with something like: $ git show 195c7a52b76d:arch/arm/mach-omap2/mux34xx.c and $ git show 195c7a52b76d:arch/arm/mach-omap2/mux34xx.h So probably as long as we only define the register name, and not the mode names, we should be good to go. And making the macro use separate pinconf and mode values would make things easier eventually to switch to use #pinctrl-cells = <2> instead of <1> later on. Regards, Tony
