alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
d817841cea
esp-idf/components/newlib/platform_include/sys/lock.h

52 lines
1.7 KiB
C
Raw Normal View History

components: Change copyright in components files
2022-06-17 10:59:56 -04:00
/*
refactor(core): reformat newlib and pthread with astyle
2024-02-26 21:00:06 -05:00
* SPDX-FileCopyrightText: 2022-2024 Espressif Systems (Shanghai) CO LTD
components: Change copyright in components files
2022-06-17 10:59:56 -04:00
*
* SPDX-License-Identifier: Apache-2.0
*/
newlib: add _RETARGETABLE_LOCKING support This adds support for the retargetable locking implementation in newlib 3. This feature will be enabled in the future toolchain builds. With the present version of the toolchain, this code doesn't get used. When _RETARGETABLE_LOCKING gets enabled, newlib locking implementation will be modified as follows: - Legacy ESP-specific _lock_xxx functions are preserved. This is done because ROM copies of newlib in ESP32 and ESP32-S2 rely on these functions through the function pointer table. Also there is some code in IDF which still uses these locking functions. - New __retarget_lock_xxx functions are introduced. Newlib expects these functions to be provided by the system. These functions work pretty much the same way as the ESP-specific _lock_xxx functions, except one major difference: _lock_acquire receives the lock pointer by value, and as such doesn't support lazy initialization. - Static locks used by newlib are now explicitly initialized at startup. Since it is unlikely that these static locks are used at the same time, all compatible locks are set to point to the same mutex. This saves a bit of RAM. Note that there are still many locks not initialized statically, in particular those inside FILE structures.
2020-06-10 14:03:32 -04:00
#pragma once
#include_next <sys/lock.h>
feat(freertos): Exposed Kconfig option for configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES This commit exposes the FreeRTOS List integrity check option configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES via menuconfig.
2023-11-03 03:55:44 -04:00
#include "sdkconfig.h"
newlib: add _RETARGETABLE_LOCKING support This adds support for the retargetable locking implementation in newlib 3. This feature will be enabled in the future toolchain builds. With the present version of the toolchain, this code doesn't get used. When _RETARGETABLE_LOCKING gets enabled, newlib locking implementation will be modified as follows: - Legacy ESP-specific _lock_xxx functions are preserved. This is done because ROM copies of newlib in ESP32 and ESP32-S2 rely on these functions through the function pointer table. Also there is some code in IDF which still uses these locking functions. - New __retarget_lock_xxx functions are introduced. Newlib expects these functions to be provided by the system. These functions work pretty much the same way as the ESP-specific _lock_xxx functions, except one major difference: _lock_acquire receives the lock pointer by value, and as such doesn't support lazy initialization. - Static locks used by newlib are now explicitly initialized at startup. Since it is unlikely that these static locks are used at the same time, all compatible locks are set to point to the same mutex. This saves a bit of RAM. Note that there are still many locks not initialized statically, in particular those inside FILE structures.
2020-06-10 14:03:32 -04:00
#ifdef _RETARGETABLE_LOCKING
/* Actual platfrom-specific definition of struct __lock.
* The size here should be sufficient for a FreeRTOS mutex.
* This is checked by a static assertion in locks.c
*
feat(freertos): Exposed Kconfig option for configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES This commit exposes the FreeRTOS List integrity check option configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES via menuconfig.
2023-11-03 03:55:44 -04:00
* Note: this might need to be made dependent on whether FreeRTOS
newlib: add _RETARGETABLE_LOCKING support This adds support for the retargetable locking implementation in newlib 3. This feature will be enabled in the future toolchain builds. With the present version of the toolchain, this code doesn't get used. When _RETARGETABLE_LOCKING gets enabled, newlib locking implementation will be modified as follows: - Legacy ESP-specific _lock_xxx functions are preserved. This is done because ROM copies of newlib in ESP32 and ESP32-S2 rely on these functions through the function pointer table. Also there is some code in IDF which still uses these locking functions. - New __retarget_lock_xxx functions are introduced. Newlib expects these functions to be provided by the system. These functions work pretty much the same way as the ESP-specific _lock_xxx functions, except one major difference: _lock_acquire receives the lock pointer by value, and as such doesn't support lazy initialization. - Static locks used by newlib are now explicitly initialized at startup. Since it is unlikely that these static locks are used at the same time, all compatible locks are set to point to the same mutex. This saves a bit of RAM. Note that there are still many locks not initialized statically, in particular those inside FILE structures.
2020-06-10 14:03:32 -04:00
* is included in the build.
*/
struct __lock {
feat(freertos): Exposed Kconfig option for configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES This commit exposes the FreeRTOS List integrity check option configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES via menuconfig.
2023-11-03 03:55:44 -04:00
#if (CONFIG_FREERTOS_USE_LIST_DATA_INTEGRITY_CHECK_BYTES && CONFIG_FREERTOS_USE_TRACE_FACILITY)
refactor(core): reformat newlib and pthread with astyle
2024-02-26 21:00:06 -05:00
int reserved[29];
feat(freertos): Exposed Kconfig option for configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES This commit exposes the FreeRTOS List integrity check option configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES via menuconfig.
2023-11-03 03:55:44 -04:00
#elif (CONFIG_FREERTOS_USE_LIST_DATA_INTEGRITY_CHECK_BYTES && !CONFIG_FREERTOS_USE_TRACE_FACILITY)
refactor(core): reformat newlib and pthread with astyle
2024-02-26 21:00:06 -05:00
int reserved[27];
feat(freertos): Exposed Kconfig option for configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES This commit exposes the FreeRTOS List integrity check option configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES via menuconfig.
2023-11-03 03:55:44 -04:00
#elif (!CONFIG_FREERTOS_USE_LIST_DATA_INTEGRITY_CHECK_BYTES && CONFIG_FREERTOS_USE_TRACE_FACILITY)
refactor(core): reformat newlib and pthread with astyle
2024-02-26 21:00:06 -05:00
int reserved[23];
feat(freertos): Exposed Kconfig option for configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES This commit exposes the FreeRTOS List integrity check option configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES via menuconfig.
2023-11-03 03:55:44 -04:00
#else
refactor(core): reformat newlib and pthread with astyle
2024-02-26 21:00:06 -05:00
int reserved[21];
feat(freertos): Exposed Kconfig option for configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES This commit exposes the FreeRTOS List integrity check option configUSE_LIST_DATA_INTEGRITY_CHECK_BYTES via menuconfig.
2023-11-03 03:55:44 -04:00
#endif /* #if (CONFIG_FREERTOS_USE_LIST_DATA_INTEGRITY_CHECK_BYTES && CONFIG_FREERTOS_USE_TRACE_FACILITY) */
newlib: add _RETARGETABLE_LOCKING support This adds support for the retargetable locking implementation in newlib 3. This feature will be enabled in the future toolchain builds. With the present version of the toolchain, this code doesn't get used. When _RETARGETABLE_LOCKING gets enabled, newlib locking implementation will be modified as follows: - Legacy ESP-specific _lock_xxx functions are preserved. This is done because ROM copies of newlib in ESP32 and ESP32-S2 rely on these functions through the function pointer table. Also there is some code in IDF which still uses these locking functions. - New __retarget_lock_xxx functions are introduced. Newlib expects these functions to be provided by the system. These functions work pretty much the same way as the ESP-specific _lock_xxx functions, except one major difference: _lock_acquire receives the lock pointer by value, and as such doesn't support lazy initialization. - Static locks used by newlib are now explicitly initialized at startup. Since it is unlikely that these static locks are used at the same time, all compatible locks are set to point to the same mutex. This saves a bit of RAM. Note that there are still many locks not initialized statically, in particular those inside FILE structures.
2020-06-10 14:03:32 -04:00
};
/* Compatibility definitions for the legacy ESP-specific locking implementation.
* These used to be provided by libc/sys/xtensa/sys/lock.h in newlib.
* Newer versions of newlib don't have this ESP-specific lock.h header, and are
* built with _RETARGETABLE_LOCKING enabled, instead.
*/
typedef _LOCK_T _lock_t;
void _lock_init(_lock_t *plock);
void _lock_init_recursive(_lock_t *plock);
void _lock_close(_lock_t *plock);
void _lock_close_recursive(_lock_t *plock);
void _lock_acquire(_lock_t *plock);
void _lock_acquire_recursive(_lock_t *plock);
int _lock_try_acquire(_lock_t *plock);
int _lock_try_acquire_recursive(_lock_t *plock);
void _lock_release(_lock_t *plock);
void _lock_release_recursive(_lock_t *plock);
#endif // _RETARGETABLE_LOCKING
Reference in New Issue Copy Permalink