Merge pull request #14031 from arduino/blockdevices_namespaces ...

BlockDevices: specify mbed namespace where needed

CMake: rename greentea test macro

fix namespaces for MBED_NO_GLOBAL_USING_DIRECTIVE feature ...

added namespaces in various files

Remove lock from enable_* function overrides

Implement override of enable_* functions

Add declaration to expose enable_* functions from SerialBase ...

UnBufferedSerial is missing a declaration to expose enable_input and
enable_output, which are inherited from the private base class Serial
Base. Add the using-declaration to the class definition.

Merge pull request #14020 from pea-pod/stm-spi-more-bits ...

Add SPI bitwidths to ST targets where supported

Add SPI bitwidths to ST targets where supported

Add CMake support

Add internal subfolder to USBDriver's CMakelists ...

To build USB Drivers for targets which have USBDevice attribute,
subfolder added as header file path.

CMake: Remove TODO note in device_key list input source file ...

The Device Key API is a security API that relies on storage. It is not a storage API

Merge pull request #13908 from LDong-Arm/kvstore_libraries ...

Restructure KVStore to one library per store type

Merge pull request #13917 from LDong-Arm/move_SFDP ...

Move SFDP to blockdevice

CMake: add missing linkages of storage libraries

CMake fix: SFDP already moved to BlockDevice

Update include paths

Merge pull request #14005 from kjbracey-arm/teinsert ...

Correct/clarify TimerEvent::insert documentation

Correct/clarify TimerEvent::insert documentation ...

There was much confusion over the functionality of the original
`TimerEvent::insert` call which was described as "Set relative timestamp
of the internal event".

This then extended to my Chrono conversion, meaning the new `insert`
call is not equivalent.

Clarify the original documentation, correct the deprecation messages,
and add more notes on conversion.

No functional change, as the new Chrono API makes more sense - it's just
different from the old API.

Problem actually spotted when I saw the strange code `convert_timestamp`
was producing for the 32-bit->64-bit timestamp conversion. The caller of
it was actually making the mistake of issuing
"TimerEvent::insert(rel_timeout)`, meaning they'd also misunderstood the
documentation, and were not getting the timeout they expected.

(Chrono would have prevented that mistake as durations and time points
are incompatible types).

Move SFDP unit tests

Move SFDP into blockdevice where it belongs to

Merge pull request #13947 from LDong-Arm/erase_algorithm_fix ...

Fix erase type determination for [Q/O/]BlockDevice::erase()

Fix integer type warnings in SFDP and *SPIFBlockDevice

Initial unit test for SFDP ...

As a starting point, only sfdp_iterate_next_largest_erase_type(),
which the pull request is intended to fix, is tested. More test
cases shall be added in the future.

sfdp_iterate_next_largest_erase_type: return -1 if no erase type is applicable

sfdp_iterate_next_largest_erase_type: do not modify type_mask ...

The supported erase types of a given flash region are indicated
in bitfields of the variable `type_mask`. Even if an erase type
is unused for the current chunk (e.g. size too large, unaligned, etc.),
its bitfield should NOT be cleared - the same erase type might
actually be useful for the next chunk.

The function argument is now a value instead of a reference.

Merge pull request #13085 from pea-pod/remove-deprecated-mbed-assert ...

Change MBED_STATIC_ASSERTs version for built-in

sfdp_iterate_next_largest_erase_type: fix size check and add alignment check

Updated CMakeLists.txt

Moved USB greentea tests

Moved USB drivers under drivers/usb