Closed carlescufi closed 7 years ago
Any idea what introduced this? I've seen it for the last few days
@MaureenHelm seems like this commit by you is the culprit after bisecting: 6312b0e6a129b9b5724e4993925b6e26c0ae2f0e
This problem seems limited to Nordic boards, as I don't see it happening on NXP or ST boards. Most of the clock control drivers are conditioned upon the SoC series, except for the NXP clock control driver which uses a depends on HAS_MCUX_SIM
instead. I think the problem may be that the Nordic SoCs select CLOCK_CONTROL
in Kconfig.series whereas everything else does it in defconfigs.
@MaureenHelm thanks for looking into this. I tried selecting CLOCK_CONTROL in the board defconfig, but the problem is that our SoC requires clock control by default because it includes the NRF_TIMER, which replaces the SysTick and itself uses the clock control, so I don't think that's a solution, since clock control is an integral part of our SoCs and should indeed be in the Kconfig.series
Can you do it in the SoC defconfig rather than the board defconfig? Although Kinetis doesn't use clock control to replace the SysTick, it does need clock control for the uart and thus the console. So it's pretty essential for Kinetis too.
Addressed by: https://github.com/zephyrproject-rtos/zephyr/pull/4663
@MaureenHelm can you take a look?
Fixed and merged by #4663
@MaureenHelm can you take a look?
LGTM. Thanks!