summaryrefslogtreecommitdiff
path: root/docs/feature_rgblight.md
diff options
context:
space:
mode:
authorRyan <fauxpark@gmail.com>2023-08-15 20:06:57 +1000
committerGitHub <noreply@github.com>2023-08-15 11:06:57 +0100
commit1c069b13b9c410d30cb3b0126b21b984284c405c (patch)
treee1c8ed8a6e4a50fb7afb8fe9b017743f0b0b87c9 /docs/feature_rgblight.md
parent3ece80f73f781a719ea6665af1d01b99922388e9 (diff)
rgblight: driver selection cleanups (#21558)
Diffstat (limited to 'docs/feature_rgblight.md')
-rw-r--r--docs/feature_rgblight.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_rgblight.md b/docs/feature_rgblight.md
index fef856f7df..39b7e6a6f1 100644
--- a/docs/feature_rgblight.md
+++ b/docs/feature_rgblight.md
@@ -28,7 +28,7 @@ For APA102 LEDs, add the following to your `rules.mk`:
```make
RGBLIGHT_ENABLE = yes
-RGBLIGHT_DRIVER = APA102
+RGBLIGHT_DRIVER = apa102
```
At minimum you must define the data pin your LED strip is connected to, and the number of LEDs in the strip, in your `config.h`. For APA102 LEDs, you must also define the clock pin. If your keyboard has onboard RGB LEDs, and you are simply creating a keymap, you usually won't need to modify these.