tree feee66081934ef3be5dc737af86d2bd2038ff64e
parent 31a3f6f0076228d8fa71d1a03f38d3daf7644b11
author Ewout van Bekkum <ewout@google.com> 1636577418 -0800
committer CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> 1636652616 +0000

pw_sync_threadx: Rolls back the ThreadNotification backend

It turns out the approach chosen to attempt to implement an optimized
ThreadNotification backend on ThreadX will fundamentally never work.

Unfortunately the kernel must have a saturating thread notification
mechanism which permits a thread to start receiving potential
notifications when the thread handle is registered. This is not
possible with the ThreadX API.

Lastly, event flags are equal to or larger than the binary
semaphores, and ergo we recommend using the binary semaphore backend
for thread notifications.

Change-Id: Ifa149296dd77b60b303552c0c008dee2cea46fc2
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/68180
Reviewed-by: Keir Mierle <keir@google.com>
Commit-Queue: Ewout van Bekkum <ewout@google.com>
Pigweed-Auto-Submit: Ewout van Bekkum <ewout@google.com>