aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBrian Low <github@brianlow.com>2021-06-15 23:07:03 -0600
committerGitHub <noreply@github.com>2021-06-15 22:07:03 -0700
commit968e4f96a49d81fdc3dbc063fc5dcfa9a2c89ade (patch)
treedf194ac1ad255a0d833d12cbcec0825948774ed7
parent311cf865dca25f3d72095d271de5d8acbe4d2150 (diff)
downloadqmk_firmware-968e4f96a49d81fdc3dbc063fc5dcfa9a2c89ade.tar.gz
qmk_firmware-968e4f96a49d81fdc3dbc063fc5dcfa9a2c89ade.zip
Top level heading for common config (RGB Matrix) (#13120)
* Top level heading for common config Prior to this, the some of the common config looks like a detail of the APA102 driver * Change heading to Common Config (RGB Matrix)
-rw-r--r--docs/feature_rgb_matrix.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/feature_rgb_matrix.md b/docs/feature_rgb_matrix.md
index 169443fb8..bfb3688b6 100644
--- a/docs/feature_rgb_matrix.md
+++ b/docs/feature_rgb_matrix.md
@@ -229,6 +229,8 @@ Configure the hardware via your `config.h`:
229 229
230--- 230---
231 231
232## Common Configuration :id=common-configuration
233
232From this point forward the configuration is the same for all the drivers. The `led_config_t` struct provides a key electrical matrix to led index lookup table, what the physical position of each LED is on the board, and what type of key or usage the LED if the LED represents. Here is a brief example: 234From this point forward the configuration is the same for all the drivers. The `led_config_t` struct provides a key electrical matrix to led index lookup table, what the physical position of each LED is on the board, and what type of key or usage the LED if the LED represents. Here is a brief example:
233 235
234```c 236```c