mbed-os

Commit Graph

Author	SHA1	Message	Date
Alastair D'Silva	aa80b7c70a	Don't use define checks on DEVICE_FOO macros (partner code) The DEVICE_FOO macros are always defined (either 0 or 1). This patch replaces any instances of a define check on a DEVICE_FOO macro with value test instead. Signed-off-by: Alastair D'Silva <alastair@d-silva.org>	2018-12-20 20:02:29 +11:00
Brian Daniels	24a9a4824f	Fixes linking errors when building with debug profile When building with the debug profile, certain ST plaforms error with 'get_i2c_timing' not being defined. This is because the function is not defined as 'static inline', but just 'inline'.	2017-01-12 15:09:28 -06: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

Alastair D'Silva

aa80b7c70a

Don't use define checks on DEVICE_FOO macros (partner code)

The DEVICE_FOO macros are always defined (either 0 or 1).

This patch replaces any instances of a define check on a DEVICE_FOO
macro with value test instead.

Signed-off-by: Alastair D'Silva <alastair@d-silva.org>

2018-12-20 20:02:29 +11:00

Brian Daniels

24a9a4824f

Fixes linking errors when building with debug profile

When building with the debug profile, certain ST plaforms error with
'get_i2c_timing' not being defined. This is because the function is not
defined as 'static inline', but just 'inline'.

2017-01-12 15:09:28 -06: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

3 Commits (feature-bluetooth-unit-test)