Lines Matching refs:be
21 This needs to be done before making any other LVGL calls.
62 be used as they are. For example:
74 ISR, it should be from either a high priority interrupt or an interrupt that
75 cannot be missed when the system is under high load.
77 .. note:: :cpp:func:`lv_tick_inc` is only one of two LVGL functions that may be
81 Either way, the writing of the ``uint32_t`` Tick value must be :ref:`atomic <atomic>`,
83 system (causing the update of the Tick value to not be atomic) and your platform uses
103 * where it can be written to any destination. */
110 Advancing the tick value should be done in such a way that its timing is reliable and
112 what *not* to do: this can "seem" to work, but LVGL's timing will be incorrect
114 thus the delay it introduces cannot be known.
129 LVGL needs to be supplied with knowledge about each display panel you want it to use.
144 LVGL needs to know how to get input from all user-input devices that will be used in