Commit da9fda43 authored by Rene van Paassen's avatar Rene van Paassen Committed by Dmitry Torokhov

Input: aiptek - use only absolute misc reports

To get an on - off reporting for proximity, absolute misc reports are
used. The mixture of absolute and relative reports is awkward
Signed-off-by: default avatarRene van Paassen <rene.vanpaassen@gmail.com>
Signed-off-by: default avatarDmitry Torokhov <dtor@mail.ru>
parent 6125a400
...@@ -417,6 +417,9 @@ static const char *map_val_to_str(const struct aiptek_map *map, int val) ...@@ -417,6 +417,9 @@ static const char *map_val_to_str(const struct aiptek_map *map, int val)
* Proximity. Why two events? I thought it interesting to know if the * Proximity. Why two events? I thought it interesting to know if the
* Proximity event occurred while the tablet was in absolute or relative * Proximity event occurred while the tablet was in absolute or relative
* mode. * mode.
* Update: REL_MISC proved not to be such a good idea. With REL_MISC you
* get an event transmitted each time. ABS_MISC works better, since it
* can be set and re-set. Thus, only using ABS_MISC from now on.
* *
* Other tablets use the notion of a certain minimum stylus pressure * Other tablets use the notion of a certain minimum stylus pressure
* to infer proximity. While that could have been done, that is yet * to infer proximity. While that could have been done, that is yet
...@@ -639,7 +642,7 @@ static void aiptek_irq(struct urb *urb) ...@@ -639,7 +642,7 @@ static void aiptek_irq(struct urb *urb)
aiptek->curSetting.wheel = AIPTEK_WHEEL_DISABLE; aiptek->curSetting.wheel = AIPTEK_WHEEL_DISABLE;
} }
} }
input_report_rel(inputdev, REL_MISC, p | AIPTEK_REPORT_TOOL_MOUSE); input_report_abs(inputdev, ABS_MISC, p | AIPTEK_REPORT_TOOL_MOUSE);
input_sync(inputdev); input_sync(inputdev);
} }
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment