On 11.05.23 11:45, Krzysztof Kozlowski wrote: > On 10/05/2023 15:50, Javier Carrasco wrote: >> The virtual-touchscreen object defines an area within the touchscreen >> where touch events are reported and their coordinates get converted to >> the virtual origin. This object avoids getting events from areas that >> are physically hidden by overlay frames. >> >> For touchscreens where overlay buttons on the touchscreen surface are >> provided, the virtual-buttons object contains a node for every button >> and the key event that should be reported when pressed. > > Hm, I don't understand - are these separate physical buttons? If so, why > would they be part of touchscreen? Where do the wires go? Those buttons are actually printed on some overlays which are mounted on top of the touchscreen and they are used to provide a predefined functionality to that touchscreen region. Any touchscreen with such a physical overlay with buttons printed on them or clipped touchscreen areas might use this functionality. These buttons are actually physical i.e. printed and with a given functionality, but still part of the touchscreen as the physical device is not aware of them. Therefore they only make sense in the touchscreen context. > >> >> Signed-off-by: Javier Carrasco <javier.carrasco@xxxxxxxxxxxxxx> >> --- >> .../bindings/input/touchscreen/touchscreen.yaml | 54 ++++++++++++++++++++++ >> 1 file changed, 54 insertions(+) >> > > Best regards, > Krzysztof >
