stbenn opened a new issue, #14551:
URL: https://github.com/apache/nuttx/issues/14551
### Description
There seems to be two naming conventions when defining macros for STM32
boards:
1. Identifiers typically omit chip type, and start with `STM32_`
- An example would be the STM32H7. In `arch/arm/src/stm32h7/hardware/`,
and the `board.h` file for the nucleo-h743zi
(`boards/arm/stm32h7/nucleo-h743zi/include/board.h`
1. Identifiers typically include chip type, and start with `STM32XX_`
- An example would be the STM32L5. In `arch/arm/src/stm32l5/hardware/`,
and the `board.h` file for nucleo-l552ze
(`boards/arm/stm32l5/nucleo-l552ze/inclue/board.h`
I cannot figure out why some chips use the first style, and some use the
second.
Are the differences between these naming conventions purely stylistic, or
are there specific reasons to use one convention instead of the other?
When adding support for a new STM32 chip family, which naming convention
would be preferred?
### Verification
- [X] I have verified before submitting the report.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
