[AshleysBrain]

No, I don't think it makes any sense at all. CPUs/OSs have built-in mechanisms to automatically adjust frequency depending on the actual workload. If scrolling involves a minimal workload then it should remain in low-power state. This is a really power-hostile solution to solving a problem which should be solved another way. At the very least, if this really is an intractable lag problem (which I doubt - other manufacturers seem unaffected), then the driver should call an OS API that says something like "latency-sensitive user input has started/stopped", and then the OS makes the decision about whether to boost the CPU frequency, or do something more sensible, or be updated in future to use new hardware features to solve the problem even better, etc.

This particular hack is just poor engineering. And users should at least be given the choice between "drain my battery or add a bit of lag", if the manufacturer can't figure out how to remove the need to make that choice.