[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <280ab18d-bbfa-9920-5f1b-d069fd866e1f@linaro.org>
Date: Thu, 11 May 2023 11:45:28 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Javier Carrasco <javier.carrasco@...fvision.net>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
Henrik Rydberg <rydberg@...math.org>,
Bastian Hecht <hechtb@...il.com>,
Michael Riesch <michael.riesch@...fvision.net>
Cc: linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH 2/4] dt-bindings: touchscreen: add virtual-touchscreen and
virtual-buttons properties
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?
>
> Signed-off-by: Javier Carrasco <javier.carrasco@...fvision.net>
> ---
> .../bindings/input/touchscreen/touchscreen.yaml | 54 ++++++++++++++++++++++
> 1 file changed, 54 insertions(+)
>
Best regards,
Krzysztof
Powered by blists - more mailing lists