Add new mouse "Ploopy Nano 2 Trackball"

[ploopyco]

This PR adds the Ploopy Nano 2 Trackball, which is an upgrade of the Nano Trackball and uses the PAW-3222 driver.

EDIT: This PR used to contain code pertaining to the PAW-3222, which has since been moved to PR #25763. This PR will remain as a draft until #25763 has been merged.

Description

The Nano 2 is an upgrade over the original Nano. It includes a new button and utilizes the PAW-3222 sensor.

Types of Changes

• [ ] Core
• [ ] Bugfix
• [ ] New feature
• [ ] Enhancement/optimization
• [x] Keyboard (addition or update)
• [x] Keymap/layout (addition or update)
• [ ] Documentation

Issues Fixed or Closed by This PR

Checklist

• [x] My code follows the code style of this project: C, Python
• [x] 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.
• [x] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[ploopyco]

Understood. Will redo into two PRs.

Edit: Will that actually work? If I open up a PR for the keyboard code and it's dependent on the code that's in this PR, I'm pretty sure that will fail the CI checks.

[waffle87]

Will that actually work? If I open up a PR for the keyboard code and it's dependent on the code that's in this PR, I'm pretty sure that will fail the CI checks.

You can open the keyboard PR as a draft PR and make note it depends on the sensor support PR to be merged first.

[tzarc]

Just for safety’s sake, can you send me a copy of the release waiver anyway? Want to confirm wording and the like. Through Discord is fine.

[ploopyco]

The PAW-3222 sensor code has been migrated to PR #25763. This PR is now only for the Nano 2 Trackball, which will remain as a draft until the PAW-3222 code has been merged.

[beaudrychase]

A small request before this is merged. Could the firmware built by default allow you to enter the bootloader by holding the button down while plugging it in?

https://github.com/ploopyco/nano-2-trackball/blob/master/firmwares/nano2_dragscroll_toggle.uf2 This firmware has that feature supported. I was surprised after flashing the firmware I built that I could no longer access the bootloader without opening the device.

[ploopyco]

Should I still be targeting develop? Also, I'm guessing that the core tag is causing a more protracted CI build to run, but this shouldn't really require it. Perhaps removing the core tag would make the PR more sensible.

[zvecr]

Should I still be targeting develop?

Yes, as you have a dependency on the driver you added, and that is not currently in master.

Also, I'm guessing that the core tag is causing a more protracted CI build to run, but this shouldn't really require

CI is not driven by labels, so this is not the case. This can be seen in the various build outputs only running against the keyboard added in this PR.

Perhaps removing the core tag would make the PR more sensible.

Usually labeler job would manage this but it seems to get confused sometimes. It wont make any difference outside filtering in the UI, but its been removed.

[zvecr]

This can now go to master as the last develop merge included #25763.