third_party.pigweed.src/pw_sync_threadx/docs.rst
Ewout van Bekkum f680eb1df6 pw_sync_threadx: allow a custom pw::chrono::SystemClock backend
Modifies the GN implementation for pw_sync_threadx to allow a
custom backend for pw::chrono::SystemClock which is not
pw_chrono_threadx:system_clock in case the TX time capability is
not enabled in a ThreadX configuration.

Change-Id: I1a4191425b4d2679472a86a388085c0ab64bedbe
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/28560
Reviewed-by: Keir Mierle <keir@google.com>
Commit-Queue: Ewout van Bekkum <ewout@google.com>
2021-01-06 21:26:57 +00:00

14 lines
507 B
ReStructuredText

.. _module-pw_sync_threadx:
---------------
pw_sync_threadx
---------------
This is a set of backends for pw_sync based on ThreadX. It is not ready for use,
and is under construction.
It is possible, if necessary, to use pw_sync_threadx without using the Pigweed
provided pw_chrono_threadx in case the ThreadX time API (``tx_time_get()``)) is
not available (i.e. ``TX_NO_TIMER`` is set). You are responsible for ensuring
that the chrono backend provided has counts which match the ThreadX tick based
API.