You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The rationale is that you may want to have API that works for one peripheral,
e.g. TIM2, but not for the others. You can only enforce that if you have
different types for the peripherals. Another similar use case is APIs that
depend on some specific combinations of peripherals: PWM1 = GPIOA + TIM2, PWM2 =
GPIOB + TIM3, etc.
The text was updated successfully, but these errors were encountered:
Right now, when dealing with derived peripherals, svd2rust uses type aliases:
Thus all both the base peripheral and the derived peripherals have the same
type.
I propose we change svd2rust to generate a different type for each peripheral.
The rationale is that you may want to have API that works for one peripheral,
e.g. TIM2, but not for the others. You can only enforce that if you have
different types for the peripherals. Another similar use case is APIs that
depend on some specific combinations of peripherals: PWM1 = GPIOA + TIM2, PWM2 =
GPIOB + TIM3, etc.
The text was updated successfully, but these errors were encountered: