Re: [PATCH 4/8] HID: input: use the Resolution Multiplier for high-resolution scrolling

From: Harry Cutts
Date: Mon Nov 26 2018 - 21:17:33 EST

On Thu, 22 Nov 2018 at 15:28, Peter Hutterer <peter.hutterer@xxxxxxxxx> wrote:
> The choices we have now are:
> - use 1200 or 12000 internally and divide by 10 before sending the
> final value
> - just make the evdev API use 1200 or 12000 and let userspace deal with it.
> much simpler.
> Any suggestions/comments?

The second option seems cleaner to me, as then we don't have multiple
representations of the scroll amount to get mixed up.

Harry Cutts
Chrome OS Touch/Input team