lkml.org 
[lkml]   [2015]   [Mar]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH v3 0/4] input: ft5x06: Fix userspace reported maximum value
Date
Hi,

The current ft5x06 reports to the user-space that its maximum
coordinates are, on both X and Y, way higher than what could be
actually usable on the screen (in my case, 5759x1151 instead of
480x800).

This causes trouble on some userspace stacks that then try to re-scale
these coordinates back to the framebuffer resolution, like QT does.

Use the of_touchscreen code to find the real touchscreen limits in the
DT case, and report that to the userspace.

Thanks,
Maxime

Changes from v2:
- Rebased on top of 4.0-rc1

Changes from v1:
- Do not use input_set_abs_params anymore to avoid enabling an axis
that was not enabled by the driver itself in of_touchscreen
- Emit a warning when an axis is set in the DT but not enabled in
the driver
- Remove EV_SYN from the edt-ft5x06 driver

Maxime Ripard (4):
input: touchscreen: of: Use input_set_abs_params
input: touchscreen: of: Register multitouch axes
input: ft5x06: Allow to set the maximum axes value through the DT
input: edt-ft5x06: Remove EV_SYN event report

drivers/input/touchscreen/edt-ft5x06.c | 6 ++-
drivers/input/touchscreen/of_touchscreen.c | 62 +++++++++++++++++++++++++-----
2 files changed, 57 insertions(+), 11 deletions(-)

--
2.3.0



\
 
 \ /
  Last update: 2015-03-03 15:21    [W:0.117 / U:0.244 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site