Lines Matching +full:lvgl +full:- +full:encoder +full:- +full:input
3 Input chapter
6 The input subsystem provides an API for dispatching input events from input
9 Input Events
12 The subsystem is built around the :c:struct:`input_event` structure. An input
19 multi-axis device have been reported.
21 Input Devices
24 An input device can report input events directly using :c:func:`input_report`
25 or any related function; for example buttons or other on-off input entities
48 on the :kconfig:option:`CONFIG_INPUT_MODE` option. If the input thread is used,
49 all the events are added to a queue and executed in a common ``input`` thread.
50 If the thread is not used, the callback are invoked directly in the input
61 A common use case for input devices is to use them to generate HID reports. For
63 :c:func:`input_to_hid_modifier` functions can be used to map input codes to HID
69 - :dtcompatible:`adc-keys`: for buttons connected to a resistor ladder.
70 - :dtcompatible:`analog-axis`: for absolute position devices connected to an
71 ADC input (thumbsticks, sliders...).
72 - :dtcompatible:`gpio-kbd-matrix`: for GPIO-connected keyboard matrices.
73 - :dtcompatible:`gpio-keys`: for switches directly connected to a GPIO,
75 - :dtcompatible:`gpio-qdec`: for GPIO-connected quadrature encoders.
76 - :dtcompatible:`input-keymap`: maps row/col/touch events from a keyboard
78 - :dtcompatible:`zephyr,input-longpress`: listens for key events, emits events
80 - :dtcompatible:`zephyr,input-double-tap`: listens for key events, emits events
81 for input double taps
82 - :dtcompatible:`zephyr,lvgl-button-input`
83 :dtcompatible:`zephyr,lvgl-encoder-input`
84 :dtcompatible:`zephyr,lvgl-keypad-input`
85 :dtcompatible:`zephyr,lvgl-pointer-input`: listens for input events and
86 translates those to various types of LVGL input devices.
94 gpio-kbd.rst
102 Input Event Definitions