4 Commits (8e3c5f11d4cc080fbf3f94f7ae6298b3fa55855c)

Author	SHA1	Message	Date
jeromecoutant	6f25e46181	STM32F0: code alignment ... No impact, no change	2020-12-03 17:15:31 +01:00
jeromecoutant	6066e68ec6	TARGET_STM32F0 astyle	2018-06-27 14:23:31 +02:00
Laurent MEUNIER	0aeea4950c	[STM32] Deploy SPI_ASYNCH to all family ... the SPI_ASYNCH feature has been already activated for STM32F4. This patchset makes it supported on all STM32 families by: - moving spi_s structure at family level instead of board level - using the F4 spi_api.c reference implementation and making it a common stm_spi_api.c file which makes maintenance a lot easier. - the only part that needs to be implemented for each family is the computation of the clock frequency input to the spi peripheral which is not the same accross families. So this is what remains in the spi_api.c of each family. Because of the introduction of the common file, all the above modifications needs to be done at once.	2016-10-13 14:18:21 +02:00
Christopher Haster	0bad622a16	restructure - Moved targets out to top level ... hal/targets -> targets hal/targets.json -> targets/targets.json	2016-09-30 19:18:09 -05:00