[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9d898a98-cb7d-45d8-80c2-2ef428288e6b@gmail.com>
Date: Mon, 22 Apr 2024 13:22:58 +0200
From: Gregor Riepl <onitake@...il.com>
To: Javier Carrasco <javier.carrasco@...fvision.net>,
Hans de Goede <hdegoede@...hat.com>
Cc: linux-input@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>, Jeff LaBundy
<jeff@...undy.com>, Conor Dooley <conor+dt@...nel.org>,
Bastian Hecht <hechtb@...il.com>,
Michael Riesch <michael.riesch@...fvision.net>
Subject: Re: [PATCH v9 0/4] Input: support overlay objects on touchscreens
> In order to generate proper key events by overlay buttons and adjust the
> touch events to a clipped surface, this series offers a documented,
> device-tree-based solution by means of helper functions.
> An implementation for a specific touchscreen driver is also included.
I believe there's at least some x86 tablets that have such a layout, so
maybe ACPI bindings would also make sense? Or can this be supported by
your DT-based solution?
I'm not sure if it would really be needed for existing devices, though.
It's possible they were all handled by touchscreen controller firmware
so far.
Hans, do you remember if we've encountered any Silead or Goodix devices
where the soft button overlay didn't work due to missing firmware support?
Powered by blists - more mailing lists