Hello input people,
Recently I've been bringing up the touchstick hardware in the Dell
Latitude E7470 and have noticed that the existing drivers for this sort
of input device typically expose EV_REL events. Unfortunately,
it seems that exposing the hardware in this way leads to some rather
unfortunate hacks. Namely, you find things like this in the Alps driver,
/*
* The x and y values tend to be quite large, and when used
* alone the trackstick is difficult to use. Scale them down
* to compensate.
*/
x /= 8;
y /= 8;
input_report_rel(dev, REL_X, x);
input_report_rel(dev, REL_Y, -y);
Seeing this made me think back to experiences with touchsticks in
previous Dell laptops, which require an annoyingly high force to begin
movement. This is presumably due to the fact that the bottom few bits of
resolution are being needlessly thrown away.
Unfortunately, it doesn't seem that relative devices currently have much
choice but to scale their input space; it seems there is no way for a
device to expose its "range" to user mode (as you might do with
input_set_abs_params in the case of an absolute device).
Honestly, it's not even clear to me that touchstick devices should
produce relative events. It seems like they are somewhere between a
touchpad and mouse. Like a mouse, there is no absolute mapping between
points in the input device space and the work space. However, like a
touchpad the input space is bounded.
Perhaps these devices should instead produce absolute events and be
marked with INPUT_PROP_POINTING_STICK so that user land code can produce
the expected relative behavior normalized to the range of the device.
Has this been considered in the past?
Alternatively, perhaps relative devices ought to also be able to expose
their range.
Regardless of what happens, it would be great if some guidance for
touchsticks could be added to the "Guidelines" section of the kernel's
Documentation/input/event-codes.txt.
Cheers,
Ben
Attachment:
signature.asc
Description: PGP signature
