aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c
diff options
context:
space:
mode:
authorJavier Carrasco <[email protected]>2024-10-16 04:02:41 +0000
committerDmitry Torokhov <[email protected]>2025-07-27 08:41:21 +0000
commitea4d331050b4cd43e6a900937db88b01ef75e1f2 (patch)
tree3a4e52b1455d64e6b05599463934f46d58dcb826 /drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c
parentdt-bindings: touchscreen: add touch-overlay property (diff)
downloadkernel-ea4d331050b4cd43e6a900937db88b01ef75e1f2.tar.gz
kernel-ea4d331050b4cd43e6a900937db88b01ef75e1f2.zip
Input: touch-overlay - add touchscreen overlay handling
Some touch devices provide mechanical overlays with different objects like buttons or clipped touchscreen surfaces. In order to support these objects, add a series of helper functions to the input subsystem to transform them into overlay objects via device tree nodes. These overlay objects consume the raw touch events and report the expected input events depending on the object properties. Note that the current implementation allows for multiple definitions of touchscreen areas (regions that report touch events), but only the first one will be used for the touchscreen device that the consumers typically provide. Should the need for multiple touchscreen areas arise, additional touchscreen devices would be required at the consumer side. There is no limitation in the number of touch areas defined as buttons. Reviewed-by: Jeff LaBundy <[email protected]> Signed-off-by: Javier Carrasco <[email protected]> Link: https://lore.kernel.org/r/20241016-feature-ts_virtobj_patch-v11-2-b292a1bbb0a1@wolfvision.net Signed-off-by: Dmitry Torokhov <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c')
0 files changed, 0 insertions, 0 deletions