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

rxInterrupt to work for all CAN instances

Merge pull request #14336 from AGlass0fMilk/polymorphic-can ...

Implement polymorphism for CAN driver

Replace NonCopyable in CAN inheritance. ...

This commit moves the deletion of copy constructor and copy assignment operators to the `mbed::interface::can` class, where both `mbed::CAN` and `mbed::interface::CAN` inherit enum types from. This allows `NonCopyable` to be removed from the inheritance list.

Fix astyle CI failures

Make interface::CAN buildable on targets without DEVICE_CAN ...

This commit adds provisions to enable using interface::CAN on targets that don't have DEVICE_CAN set to 1 (ie: they don't normally have a CAN peripheral).

Enable inheritance of CAN enum types ...

This commit changes the `interface::can` namespace to a `struct`. This allows the enum types to be inherited and prevents breaking old code relying on referencing eg: `CAN::RxIrq`.

When enabled, the polymorphic CAN interface class inherits from this `interface::can` struct. If not enabled, the `mbed::CAN` class inherits from `interface::can` directly.

Co-authored-by: Vincent Coubard <vincent.coubard@arm.com>

Implement polymorphism for CAN

Add v8.1-M architecture awareness ...

Add v8.1-M architecture awareness to Mbed CRC, HAL, and Mbed Atomic.

Fixes #14433

Merge pull request #14437 from ARMmbed/qspi-fix ...

Remove ownership/acquire in QSPI/OSPI driver

Remove ownership in OSPI driver

Remove ownership in QSPI driver

Remove virtual from interface operator definitions

astyle fixes

Implement polymorphism for DigitalInOut ...

Co-authored-by: Vincent Coubard (pan-) <Vincent.Coubard@arm.com>

Implement polymorphism for DigitalOut

Implement polymorphism for DigitalIn

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.

Add SPI bitwidths to ST targets where supported

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

Move SFDP to blockdevice

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 into blockdevice where it belongs to

Fix integer type warnings in SFDP and *SPIFBlockDevice

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.

Moved USB drivers under drivers/usb

Merge pull request #13699 from boraozgen/bugfix/sfdp-find-addr-region ...

Fix sfdp_find_addr_region algorithm

STM32: allow high speed USB endpoints

Fix sfdp_find_addr_region algorithm ...

sfdp_find_addr_region() was causing issues with SPI
flashes with sector table parsed from SFDP (in
particular SST26VF016B).

In particular, it was returning -1 when address 0 is
passed (probably also if the address in the first
region). I do not know why the search algorithm is
written to search from the higher to lower regions,
but it was obvious that it would fail for the first
region. Also it was harder to read due to the index
manipulation.