Does LVGL need (or can it work with) another event loop?

[embeddedt]

@detly

Is there a built-in lv_...() function that does this? I know lv_tick_inc() doesn’t need this protection, what about say, lv_task_create() ?

lv_tick_inc is the only function that has built-in protection (because you would often want to call it from an interrupt handler, etc.). All other functions need manual protection added.

@detly

Failing that, if I only call lv_ functions from the thread that runs lv_task_handler() , will that suffice?

Yes, because in that case, all LVGL code is running on one OS thread.

@detly

The way I’m thinking about it is that this exploits whatever mutexes/protection libuv or queue is using, right?

Yes; if libuv has mutexes already and you do everything through its own APIs, that should be sufficient.