inconsistent naming of macros accross families #8
Labels
cmsis
CMSIS-related issue or pull-request.
enhancement
New feature or request
internal bug tracker
Issue confirmed and reported into a ticket in the internal bug tracking system
It seems that the GPIO peripheral is largely the same for all but the STM32F1 family. Still, macros that seem to refer to the exact same thing are named inconsistently, e.g.:
GPIO_OSPEEDER_OSPEED0
: STM32L0GPIO_OSPEEDER_OSPEEDR0
: STM32F0, STM32F2, STM32F3, STM32F4, STM32F7, STM32G4, STM32L1, STM32L4GPIO_OSPEEDR_OSPEED0
: STM32F2, STM32F4, STM32G0, STM32G4, STM32L4, STM32L5, STM32U5, STM32WB, STM32WLGPIO_OSPEEDR_OSPEEDR0
: STM32F0, STM32F7Are there any plans to at least provide aliases (e.g.
#define GPIO_OSPEEDR_OSPEED0 GPIO_OSPEEDER_OSPEEDR0
) so that there is one canonical name for each macro that works across families?The text was updated successfully, but these errors were encountered: