[Bug] Fix pmw33xx sensor corruption on get-cpi call

[drashna]

Description

Initially reported by Wimads and burkfers on the BastardKB discord.

The bug with PMW3360 I was talking about a week ago or so, with DPI's of 100, 900, 1700, etc not working. We figured out it was caused by pointing_device_get_cpi() Calling that at those DPI settings, causes mouse reports to break (no reports coming in). Setting cpi right after getting it fixes the issue. So something is going wrong with the get_cpi call.

This sounds like a bug with the pmw3360 firmware itself. But for now, this is a quick fix to the issue that is confirmed to work.

Types of Changes

• Core
• Bugfix

Issues Fixed or Closed by This PR

• Issue reported on BastardKB discord

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).