|
Safe API Framework
Layered API framework for safety-related applications (ERTMS RBC reference targeting CENELEC EN 50128 SIL 4)
|
OS-backend adaptation surface for the Mutex service (ADR-033, ADR-021). More...
Go to the source code of this file.
Data Structures | |
| struct | sapi_mutex_backend_t |
| Backend vtable: an integrator's implementation of the mutex service for a specific OS/RTOS/BSP target (ADR-033). Any slot may be NULL if that operation is unsupported by the backend, in which case the corresponding sapi_mutex_* call returns SAPI_STATUS_NOT_SUPPORTED. More... | |
Functions | |
| sapi_status_t | sapi_mutex_register_backend (const sapi_mutex_backend_t *backend) |
| Registers the backend implementation used by every sapi_mutex_* call. This is how an integrator supplies their own mutex implementation - call once at startup, before any other sapi_mutex_* function. | |
OS-backend adaptation surface for the Mutex service (ADR-033, ADR-021).
This header is for platform/RTOS integrators implementing a sapi_mutex_backend_t and calling sapi_mutex_register_backend() - it is NOT part of the API a consuming application uses to create/lock/unlock mutexes (that is safeapi/mutex/sapi_mutex.h). A real application should never need to include this file; only the one piece of startup code that wires a concrete backend into the framework should.
Definition in file sapi_mutex_backend.h.