aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorQMK Bot <hello@qmk.fm>2021-06-16 05:07:37 +0000
committerQMK Bot <hello@qmk.fm>2021-06-16 05:07:37 +0000
commita61c38c7ecbd0d96500501413696778d41d9d54d (patch)
tree0c9b8ee43fc4cc3be10ad29c147be313f0f3e240
parent03f7bec6c865963ab39dc88f1f79ece1f1cc8e34 (diff)
parent875bb48a20504474e7a3627c3092d9d90b087404 (diff)
downloadqmk_firmware-a61c38c7ecbd0d96500501413696778d41d9d54d.tar.gz
qmk_firmware-a61c38c7ecbd0d96500501413696778d41d9d54d.zip
Merge remote-tracking branch 'origin/master' into develop
-rw-r--r--docs/feature_led_matrix.md2
-rw-r--r--docs/feature_rgb_matrix.md2
2 files changed, 4 insertions, 0 deletions
diff --git a/docs/feature_led_matrix.md b/docs/feature_led_matrix.md
index 9c3e2c7f3..5134ab6ef 100644
--- a/docs/feature_led_matrix.md
+++ b/docs/feature_led_matrix.md
@@ -67,6 +67,8 @@ Where `Cx_y` is the location of the LED in the matrix defined by [the datasheet]
67 67
68--- 68---
69 69
70## Common Configuration :id=common-configuration
71
70From 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: 72From 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:
71 73
72```c 74```c
diff --git a/docs/feature_rgb_matrix.md b/docs/feature_rgb_matrix.md
index afd72fecf..25ba3ffe3 100644
--- a/docs/feature_rgb_matrix.md
+++ b/docs/feature_rgb_matrix.md
@@ -297,6 +297,8 @@ const aw_led g_aw_leds[DRIVER_LED_TOTAL] = {
297 297
298--- 298---
299 299
300## Common Configuration :id=common-configuration
301
300From 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: 302From 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:
301 303
302```c 304```c