mbed-os

Commit Graph

Author	SHA1	Message	Date
Laurent MEUNIER	29b32b84b3	STM32 I2C - 1MHZ frequency is allowed So make the assert to cover all possible values Also assert applies only for I2C_IP_VERSION_V2. Also in case of I2C_IP_VERSION_V1, the HAL makes the proper checks and can dynamically scale the frequency in case of intermediate value.	2016-12-01 15:20:11 +01:00
Laurent MEUNIER	3fad50287c	[STM32] Make most of the I2C code into a common file Since most of the code in i2c_api.c is now relying on STM32 HAL, there is now a possibility to make a common usage of this code accross families. The IP version definition is introduced per family, to allow a switch of functionnalities, especially the frequency management which differs. BTw, we fix the F0 frequency settings at the same time. F1 is managed for now as an exception as the HAL API for sequential transmit /receive is not yet available (coming soon)	2016-11-30 08:23:13 +01:00

Author

SHA1

Message

Date

Laurent MEUNIER

29b32b84b3

STM32 I2C - 1MHZ frequency is allowed

So make the assert to cover all possible values
Also assert applies only for I2C_IP_VERSION_V2.
Also in case of I2C_IP_VERSION_V1, the HAL makes the proper
checks and can dynamically scale the frequency in case of
intermediate value.

2016-12-01 15:20:11 +01:00

Laurent MEUNIER

3fad50287c

[STM32] Make most of the I2C code into a common file

Since most of the code in i2c_api.c is now relying on STM32 HAL, there
is now a possibility to make a common usage of this code accross families.

The IP version definition is introduced per family, to allow a switch of
functionnalities, especially the frequency management which differs.
BTw, we fix the F0 frequency settings at the same time.

F1 is managed for now as an exception as the HAL API for sequential transmit
/receive is not yet available (coming soon)

2016-11-30 08:23:13 +01:00

1 2

52 Commits (563edb294d881c76f117760709306e1683d1018a)