Hi Javier, On 2023-04-25 13:50:45+0200, Javier Carrasco wrote: > Some touchscreens are shipped with a physical layer on top of them where > a number of buttons and a resized touchscreen surface might be available. > > In order to generate proper key events by overlay buttons and adjust the > touch events to a clipped surface, these patches offer a documented, > device-tree-based solution by means of helper functions. > An implementation for a specific touchscreen driver is also included. > > The functions in ts-virtobj provide a simple workflow to acquire > physical objects from the device tree, map them into the device driver > structures as virtual objects and generate events according to > the object descriptions. > > This solution has been tested with a JT240MHQS-E3 display, which uses > the st1624 as a touchscreen and provides two overly buttons and a frame > that clips its effective surface. There are quite a few of notebooks from Asus that feature a printed numpad on their touchpad [0]. The mapping from the touch events to the numpad events needs to happen in software. Do you think your solution is general enough to also support this usecase? The differences I see are * not device-tree based * touchpads instead of touchscreens > [..] [0] https://unix.stackexchange.com/q/494400
