diff options
Diffstat (limited to 'drivers')
| -rw-r--r-- | drivers/input/tablet/aiptek.c | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/drivers/input/tablet/aiptek.c b/drivers/input/tablet/aiptek.c index 7fb15af33c49..c7db623682de 100644 --- a/drivers/input/tablet/aiptek.c +++ b/drivers/input/tablet/aiptek.c | |||
| @@ -417,6 +417,9 @@ static const char *map_val_to_str(const struct aiptek_map *map, int val) | |||
| 417 | * Proximity. Why two events? I thought it interesting to know if the | 417 | * Proximity. Why two events? I thought it interesting to know if the |
| 418 | * Proximity event occurred while the tablet was in absolute or relative | 418 | * Proximity event occurred while the tablet was in absolute or relative |
| 419 | * mode. | 419 | * mode. |
| 420 | * Update: REL_MISC proved not to be such a good idea. With REL_MISC you | ||
| 421 | * get an event transmitted each time. ABS_MISC works better, since it | ||
| 422 | * can be set and re-set. Thus, only using ABS_MISC from now on. | ||
| 420 | * | 423 | * |
| 421 | * Other tablets use the notion of a certain minimum stylus pressure | 424 | * Other tablets use the notion of a certain minimum stylus pressure |
| 422 | * to infer proximity. While that could have been done, that is yet | 425 | * to infer proximity. While that could have been done, that is yet |
| @@ -639,7 +642,7 @@ static void aiptek_irq(struct urb *urb) | |||
| 639 | aiptek->curSetting.wheel = AIPTEK_WHEEL_DISABLE; | 642 | aiptek->curSetting.wheel = AIPTEK_WHEEL_DISABLE; |
| 640 | } | 643 | } |
| 641 | } | 644 | } |
| 642 | input_report_rel(inputdev, REL_MISC, p | AIPTEK_REPORT_TOOL_MOUSE); | 645 | input_report_abs(inputdev, ABS_MISC, p | AIPTEK_REPORT_TOOL_MOUSE); |
| 643 | input_sync(inputdev); | 646 | input_sync(inputdev); |
| 644 | } | 647 | } |
| 645 | } | 648 | } |