events: astyle fix

Introduce API to query how much time is left for delayed event ...

If user has initiated a delayed event (either with call_in or call_every),
user might need to know how much time is left until the event is
due to be dispatched.

Added time_left() function can be used to get the remaining time.

Make event queue use RTOS tick count ...

Event queue was using its own Timer or LowPowerTimer objects to derive
millisecond tick counts. This is unnecessary in RTOS builds, where the
RTOS is maintaining a tick count.

It also makes more sense to use the actual RTOS tick count, as the
values are being used to compute tick timeouts for RTOS calls. Computing
these RTOS tick delays with a separate timer could conceivably lead to
rounding errors.

Fixes: #5378

Merge pull request #6238 from pauluap/break_dispatch_flag ...

Remove windup behavior from break_dispatch

Merge pull request #6149 from bmcdonnell-ionx/typos ...

Fix typos in the files

Merge pull request #6274 from geky/events-doc-periodic ...

events: Added note about immediate firing of periodic events

Merge pull request #6286 from delftswa2018/feature-typo-fixes ...

Small typo fixes in readme.md files

Small typo fixes in readme.md files

Flip order of comparison

events: Added note about immediate firing of periodic events

Clarify intention between comparison to zero and the shift operation ...

Building with (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 7.2.1 20170904 gives this warning

../events/equeue/equeue.c: In function 'equeue_incid':
../events/equeue/equeue.c:40:17: warning: '<<' in boolean context, did you mean '<' ? [-Wint-in-bool-context]
     if (!(e->id << q->npw2)) {

style fixups

Add test to cover break_dispatch windup

Clear the break requested flag if the dispatch loop is being broken due to a timeout condition

Remove windup behavior from break_dispatch

typos

Merge pull request #6118 from ARMmbed/g-note-global-equeue-irq ...

equeue: Add note about using global event queues in irq

equeue: Added note about using global event queues in irq

equeue: Removed RTOS dependencies when RTOS not present

equeue: some refactoring to meet coding rules

equeue: added help text for new config option use-lowpower-timer-ticker

equeue: added config option which tells equeue_mbed.cpp if it shall use LowPowerTimer, LowPowerTimeout and LowPowerTicker instead of Timer/Timeout/Ticker. ...

This way, on SiLabs boards the low power sleep states will be used when using event queue.

Remove use of internal RTX types ...

Make calls to cmsis-os to get thread state, stack size, and max stack
usage rather than accessing internal RTX data directly. Wrap RTX5
specific code in OS_BACKEND_RTX5.

Also refactor the code to use mbed types rather than RTX types:
os_timer_t -> mbed_rtos_storage_timer_t
os_event_flags_t -> mbed_rtos_storage_event_flags_t
osRtxMutex_t -> mbed_rtos_storage_thread_t

Add ability to request a shared event queue ...

To allow components with a simple need to schedule a few events to not
have to create their own threads, with all the associated memory
overhead, add 2 central calls to get shared normal and an
interrupt-deferral event queues, each dispatched on their own shared
threads.

For non-RTOS systems, just the normal event queue is provided, and the
application would have to dispatch this itself. This
application-dispatch is also available via a config option, to
potentially save memory by reusing the main thread.

Possible future improvement: the ability for separate components to
request a minimum stack size, and have the JSON combine these requests.
(Analogous tooling has already been mooted for mbed TLS config options
like key size).

Merge pull request #4571 from geky/events-use-rtx-event-flags ...

events: Adopt osEventFlags from RTX 5

event: Make the event queue non copyable.

events: Adopt osEventFlags from RTX 5 ...

This provides the correct binary semaphore behaviour that was expected
by the equeue layer, removes concerns around semaphore overflow, and
reduces the number of spurious wakeups which may save a bit of power.

This also fixes some issues we were seeing around the RTX 5 changes
to semaphore behaviour.

EventQueue.h Doxygen doc fixed up. Moved overloaded callback arguments documentation to overloaded functions to fix warnings. B0..B4 were not documentated additionally, only bulk docs for a0..a4 and c0..c4 were moved around.

Removed Doxygen errors from Event.h ...

- Removed Makefile from branch
- Moved a0..a4/c0..c4 parameter documentation from top level overloaded functions to each function to appease Doxygen.
- Removed @see Event::Event from overloaded functions as the link did not work and the argument parameter documentation was moved down to each function
- TODO: Cleanup EventQueue.h

Update codebase for CMSIS5/RTX5 ...

Update all of mbed-os to use RTX5.