zephyr/doc/kernel/synchronization/synchronization.rst

.. _synchronization_v2:

Synchronization
###############

This section describes kernel services for synchronizing the operation
of different threads, or the operation of an ISR and a thread.

.. toctree::
   :maxdepth: 2

   semaphores.rst
   mutexes.rst
   alerts.rst
unified/doc: Kernel primer for unified kernel Work by: Allan Stephens Change-Id: I1f936cd6e7d592969f65330a6d204729ab0f32db Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com> 2016-09-03 03:54:16 +08:00			`.. _synchronization_v2:`

			`Synchronization`
			`###############`

			`This section describes kernel services for synchronizing the operation`
			`of different threads, or the operation of an ISR and a thread.`

			`.. toctree::`
			`:maxdepth: 2`

			`semaphores.rst`
			`mutexes.rst`
unified: rename 'events' to 'alerts' Event is such an overloaded and generic term (event logger, kernel event logger, "protocol" events in other subsystems, etc.), that it is confusing for the name an object. Events are kinda like signals, but not exactly, so we chose not to name them 'signals' to prevent further confusion. "Alerts" felt like a good fit, since they are used to "alert" an application that something of significance should be addressed and because an "alert handler" can be proactively registered with an alert. Change-Id: Ibfeb5eaf0e6e62702ac3fec281d17f8a63145fa1 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com> 2016-10-26 01:28:35 +08:00			`alerts.rst`