-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement condition variables for Mbed and FreeRTOS-Plus-TCP ports #821
Conversation
PR missing one of the required labels: {'breaking-change', 'new feature', 'documentation', 'bug', 'enhancement', 'dependencies', 'internal'} |
Co-Authored-By: Alexander Bushnev <[email protected]>
PR missing one of the required labels: {'enhancement', 'bug', 'documentation', 'dependencies', 'breaking-change', 'new feature', 'internal'} |
PR missing one of the required labels: {'bug', 'documentation', 'internal', 'breaking-change', 'enhancement', 'dependencies', 'new feature'} |
PR missing one of the required labels: {'documentation', 'new feature', 'bug', 'internal', 'breaking-change', 'dependencies', 'enhancement'} |
PR missing one of the required labels: {'documentation', 'dependencies', 'bug', 'new feature', 'breaking-change', 'internal', 'enhancement'} |
The current implementation of condition variables in mbed port is completely broken. The ConditionVariable class can't be used with z_condvar APIs as it requires passing a Mutex in the constructor. I got "inspired" by the implementation of this class and wrote a custom condition variable implementation that works with z_condvar interfaces. I also adapted this implementation for FreeRTOS-Plus-TCP port.