Lines Matching full:or
23 - each task (or process),
31 see it either as not yet started, or as completed, and not in any state that is
34 If other threads can see the operation in a partially performed state, or
46 A datum (i.e. contents of a variable or data structure) is atomic if any thread
48 have either not yet started, or have been successfully completed, and not in a
49 state that is partially changed or otherwise inconsistent.
51 When reading or writing a value is started and completed with 1 CPU instruction,
53 (partially-changed) state, even from a CPU interrupt or exception. With such
84 ``lv_``) either read from or change those data structures. Those that change them
103 LVGL functions, set a flag or other atomic value that your LVGL-calling thread
104 (or an :ref:`LVGL Timer <timer>` you create) can read from and take action.
123 data that should be shown (or otherwise reflected) in the user interface, and doing
124 so requires making LVGL calls to get that data (or change) shown.
136 A "Gateway Thread" (or "Gateway Task" in some OSes) is a thread (task) that the
138 management of a remote chip, such as an EEPROM or other device that always needs to
140 is management of multiple devices on an I2C bus (or any data bus). In this case the
160 by another task or in an interrupt), the thread calling LVGL functions can read that
167 (i.e. by another task or in an interrupt), an alternate (and safe) way of convey that
169 that thread via a QUEUE or other OS mechanism that protects that data from being seen
179 protects the state of a system resource from being modified or accessed by multiple
187 1. acquiring the MUTEX (a.k.a. locking it) before accessing or modifying that
190 2. releasing the MUTEX (a.k.a. unlocking it) after that access or modification
201 call (or group of function calls) must be preceded by #1, and followed by #2,
214 immediately with no effect, or are optimized away by the linker.