[NCS-3.1.1] NRF_RTC_TIMER: clarification

Hi,

Could you please clarify why there is an override of the checking rules in  https://github.com/nrfconnect/sdk-zephyr/blob/ncs-v3.1.1/drivers/timer/Kconfig.nrf_rtc#L6C8-L6C21  regarding the dependency on !$(dt_nodelabel_enabled,rtc1)?

For example, in my board DTS (based on nRF52833) I have:

&rtc1 { status = "okay"; };

My expectation would be that CONFIG_NRF_RTC_TIMER is set to N and that Zephyr would trigger a configuration-time error about the missing timer. However, I notice it is being forcibly set to Y by github.com/.../Kconfig.defconfig

In my opinion, this behavior is not very transparent. Could you explain the rationale behind this design choice?

Thanks,
Alessandro

Related