Added Raw CAN (unlocked can read api) and updated the code for the ...

rxInterrupt to work for all CAN instances

STM32F2: ST CUBE drivers update V1.6.0 => V1.9.2

STM32 I2C: use correct HAL API

TARGET_STM: rework hal_sleep management to be compatible with all STM32 families

STM32: pwmout_write: configure channel only when not already enabled ...

Fix PWM glitch on write(), TARGET_STM/pwmout_api.c, #10734

STM32: common cmsis.h and device.h

STM32F2: Enable TRNG

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>

STM32F2: Add Flash API support

NUCLEO_F207ZG: Fix issue with tests-api-analogout and GCC_ARM ...

Without this fix the tests-api-analogout test is fail with GCC_ARM.

STM32: F2: put can_s struct under DEVICE_CAN option ...

In case of F2 devices without CAN support.

STM32: CAN: restore registers after can_reset ...

After reset the MCR register content needs to be restored so we're
introducing the can_registers_init function to be called at the first
init stage, but also after reset. We also store the can frequency to
go through the initialisation phase again.

STM32: Define CAN handle as part of can object ...

Instead of a static object, this will make driver
instantiation more robust and allow to re-use init
configuration on a need basis.

The CANName struct member is actually the CAN registers base address,
which is now available in the CanHandle.Instance field, so we don't need
CANName anymore.

STM32: F2: adc; struct member not needed ...

Same as other families applied here

STM32: Analogin - define handle in object not as a global ...

In this commit, the analogin_s structure is moved to commonn_objects.h file
to limit the duplicaion.

The ADC handle is moved from a global variable to a struct member of the
analogin object. This allows multiple ADC instances to work correctly.

Note that State needs to be explicitely set to HAL_ADC_STATE_RESET
because the object is not zero initialized.

STM32: analog_out: generalize code for multiple instance handling ...

Moving some code in common to be able to manage several ADC instances,
or several channels of an instance.

The change involves:
- moving dac_s structure definition to common_object.h
- create TARGET_STM/analogout_api.c and move fully common analog_out
functions in there
- rename analogout_api.c of each target family into analogout_device.c
to keep platform specific code
- update analogout_device.c to rely on obj->handle and obj->channel
- align analogout_init function as much as possible between families in
analogout_device.c files

STM32: make PWM driver into a common file ...

The pwmout driver is very similar for each STM32 family.

The only family specific part is defined in pwmout_device.h file.
It mainly contains few specific information:
- The mapping of PWM/TIMERS to APB1 or APB2 so that we can get the clock
- The clock calculation uses the right APB clock, which was sometimes
not the case before and could have lead to errors in case dividers were
enabled on APB clock settings. This case is now covered.
- Inactivation of inverted support on feaw families

STM32: gpio: factorize gpio_api.c and gpio_object.h ...

Let's make the code more common for gpios.

The only difference between STM32 families is that BRR register may
not be available. In case BRR is not available, we use the 16 left bits
of BSRR instead. We could always use BSRR, but BRR saves one left-shift
operation, so let's use it when available.

By default we will consider using BRR, except for platforms that define
GPIO_IP_WITHOUT_BRR.

[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)

[stm32] remove unused module member in spi_s struct

[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.

restructure - Moved targets out to top level ...

hal/targets -> targets
hal/targets.json -> targets/targets.json