Lines Matching refs:thread

15     In the context of this document, a thread is any sequence of CPU instructions.
18     - the main thread executing a while(1) loop that runs the system, and
30     If operation X is atomic, that means that any thread observing the operation will
46     A datum (i.e. contents of a variable or data structure) is atomic if any thread
64 LVGL is **not thread-safe**.
67 called while another LVGL call is in progress in another thread.  This includes calls
76     because the thread that drives both of these is the thread that calls
94     These two LVGL functions may be called from any thread:
103     LVGL functions, set a flag or other atomic value that your LVGL-calling thread
132 .. _gateway thread:
136 A "Gateway Thread" (or "Gateway Task" in some OSes) is a thread (task) that the
141 I2C bus is the "exclusively-managed resource", and having only one thread managing it
149 <os_exception>` mentioned above) are called by that thread.  That means
150 that thread is also the ONLY caller of :cpp:func:`lv_timer_handler`.  (See
156 Thread`_ is the only thread making LVGL calls (excluding the :ref:`exceptions
159 If `atomic data`_ relevant to the user interface is updated in another thread (i.e.
160 by another task or in an interrupt), the thread calling LVGL functions can read that
163 updating thread] so that the user interface is only updated when it will result in a
166 If `non-atomic data`_ relevant to the user interface is updated in another thread
168 data to the thread calling LVGL functions is to pass a private copy of that data to
169 that thread via a QUEUE or other OS mechanism that protects that data from being seen
193 If a thread attempts to acquire (lock) the MUTEX while another thread "owns" it,
194 that thread waits on the other thread to release (unlock) it before it is allowed