Fix Meridian RGB indicators for varying hardware across PCB batches.

[holtenc]

Two different LED parts were used by the manufacturer creating a firmware issue. This update helps to correct this by making two different firmware versions. A small change was made to drivers/chibios/ws2812.c to make this possible.

WS2812 driver was also changed from SPI to bitbang due to an apparent issue with SPI introduced since the Meridian firmware was initially merged.

Types of Changes

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

Issues Fixed or Closed by This PR

#11755

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).

[zvecr]

Also v1.1 is currently an invalid keyboard name so would have to be something like v1_1

[holtenc]

build errors in continuous-integration/travis-ci/pr are due to my changes in drivers/chibios/ws2812.c not being present yet.

[zvecr]

Also as a passing comment, the rev1 now using the bitbang driver seems like a step backwards. And use of rgblight layers at the keyboard level seems a tad meh.

[holtenc]

@drashna @zvecr
Do you guys have any further revisions that need to be made? I can get that PR for /drivers/chibios/ws2812.c submitted as soon as this side is taken care of.

[holtenc]

So would it be best to just close this PR and re-submit? @zvecr @drashna

from what I can tell the structure of halconf.h and chconf.h etc have had significant changes, which I attempted to update to but that just seems to have messed this PR up.

please advise.

[drashna]

Well, updating them should be just running qmk chibosconf, I think it was.

But you roll back commits and force push, or revert them, to fix issues.

[stale]

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

[stale]

Thank you for your contribution!
This pull request has been automatically closed because it has not had activity in the last 30 days. Please feel free to give a status update now, ping for review, or re-open when it's ready.