Commit bbe1eebc has changed the order of TIM candidates when using the
time-driver-any feature. For instance, in the case of STM32F3, it
previously returned TIM2 but now returns TIM15. Consequently, the
"multiprio" example no longer works as it requires three *free* CC
register (for alarms), while TIM15 provides only one (CC1 is always
reserved for regular time keeping).
This commit was successfully tested on STM32F3. Additionally, I
verified that all the examples using a timer for STM32F0 and STM32F4
still build correctly.
Fixes#2749
6801c6496c