This is an issue for more than NXP boards and drivers, but this tracking issue is for NXP platforms only as that is what the NXP platform maintainers will commit to fixing.
The issue is that many (maybe all) NXP boards are setting CONFIG_PINCTRL=y in the board conf file. This should not have to happen because any drivers that use the pinctrl should select it automatically.
This is an issue for more than NXP boards and drivers, but this tracking issue is for NXP platforms only as that is what the NXP platform maintainers will commit to fixing.
The issue is that many (maybe all) NXP boards are setting
CONFIG_PINCTRL=y
in the board conf file. This should not have to happen because any drivers that use the pinctrl should select it automatically.Example: https://github.com/zephyrproject-rtos/zephyr/blob/dc5f1bfb3f2eee3e3775175232d508660f5d6efe/boards/nxp/frdm_mcxn947/frdm_mcxn947_mcxn947_cpu0_defconfig#L12
The only exception I found was the
twr_ke18f
board which does use pinctrl APIs in the board code itself: https://github.com/zephyrproject-rtos/zephyr/blob/dc5f1bfb3f2eee3e3775175232d508660f5d6efe/boards/nxp/twr_ke18f/pinmux.c#L11-L27