github-code/lvgl
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(intro): fix typos (#7485)

Browse Source 
Signed-off-by: bjsylvia <bjsylvia@163.com>
This commit is contained in:
bjsylvia
2024-12-20 11:06:56 +08:00
committed by GitHub
parent a903fc3d75
commit 0756895382
5 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/intro/add-lvgl-to-your-project/threading.rst
View File

@@ -175,7 +175,7 @@ MUTEX to protect LVGL data structures.
Method 2: Use a MUTEX
----------------------
A MUTEX stands for "MUTually EXclusive" and is a synchronization primative that
A MUTEX stands for "MUTually EXclusive" and is a synchronization primitive that
protects the state of a system resource from being modified or accessed by multiple
threads of execution at once. In other words, it makes data so protected "appear"
atomic (all threads using this data "see" it in a consistent state). Most OSes
@@ -198,7 +198,7 @@ To be clear: this must be done *both* by threads that READ from that resource,
threads that MODIFY that resource.
If a MUTEX is used to protect LVGL data structures, that means *every* LVGL function
call (or group of function calls) must be preceeded by #1, and followed by #2,
call (or group of function calls) must be preceded by #1, and followed by #2,
including calls to :cpp:func:`lv_timer_handler`.
.. note::